Last SLP changes

View: New views
7 Messages — Rating Filter:   Alert me  

Last SLP changes

by simonebordet :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I have committed the changes I had locally to fix a bunch of bugs,
among which the latest reported.

Alan, I have also reorganized the poms: now all OSGi dependencies are
in the osgi module and not in the parent pom.

I am in favor of fixing/implementing a couple of other bugs/features,
and then release 2.1.0 instead of releasing 2.0.2.
Comments ?

Simon
--
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Re: Last SLP changes

by Alan.Cabrera :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On Oct 19, 2009, at 6:04 AM, Simone Bordet wrote:

> Hi,
>
> I have committed the changes I had locally to fix a bunch of bugs,
> among which the latest reported.
>
> Alan, I have also reorganized the poms: now all OSGi dependencies are
> in the osgi module and not in the parent pom.

Usually all of the dependencies versions for the whole project are in  
the root pom.  But since these two modules are kinda orthogonal, in a  
way, it seems ok to push the versions up.

The a few, maybe only one, plugins in the build element are  
redundantly repeated in the modules.

>
> I am in favor of fixing/implementing a couple of other bugs/features,
> and then release 2.1.0 instead of releasing 2.0.2.
> Comments ?

Since 2.1.0 is totally backward compatible w/ 2.0.x I think that just  
releasing 2.1.0 should be fine.


Regards,
Alan


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Re: Last SLP changes

by simonebordet :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

On Mon, Oct 19, 2009 at 16:06, Alan D. Cabrera <adc@...> wrote:

>
> On Oct 19, 2009, at 6:04 AM, Simone Bordet wrote:
>
>> Hi,
>>
>> I have committed the changes I had locally to fix a bunch of bugs,
>> among which the latest reported.
>>
>> Alan, I have also reorganized the poms: now all OSGi dependencies are
>> in the osgi module and not in the parent pom.
>
> Usually all of the dependencies versions for the whole project are in the
> root pom.  But since these two modules are kinda orthogonal, in a way, it
> seems ok to push the versions up.
>
> The a few, maybe only one, plugins in the build element are redundantly
> repeated in the modules.

Sorry don't follow...
core does not depend on osgi, so I see no need to put in the root pom
a dependency management for osgi, that's why I pushed it to the osgi
module.

Which are the repeated plugins ?

Simon
--
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Re: Last SLP changes

by Alan.Cabrera :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On Oct 19, 2009, at 7:11 AM, Simone Bordet wrote:

> Hi,
>
> On Mon, Oct 19, 2009 at 16:06, Alan D. Cabrera <adc@...>  
> wrote:
>>
>> On Oct 19, 2009, at 6:04 AM, Simone Bordet wrote:
>>
>>> Hi,
>>>
>>> I have committed the changes I had locally to fix a bunch of bugs,
>>> among which the latest reported.
>>>
>>> Alan, I have also reorganized the poms: now all OSGi dependencies  
>>> are
>>> in the osgi module and not in the parent pom.
>>
>> Usually all of the dependencies versions for the whole project are  
>> in the
>> root pom.  But since these two modules are kinda orthogonal, in a  
>> way, it
>> seems ok to push the versions up.
>>
>> The a few, maybe only one, plugins in the build element are  
>> redundantly
>> repeated in the modules.
>
> Sorry don't follow...
> core does not depend on osgi, so I see no need to put in the root pom
> a dependency management for osgi, that's why I pushed it to the osgi
> module.

Since these are not shared it makes sense.  However for larger  
projects one would put all the dependencies and their versions at the  
root one knows all the deps in the project and to make sure there are  
no deps w/ different versions.

Again, in this case it's not a big deal.

>
> Which are the repeated plugins ?

             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-compiler-plugin</artifactId>
                 <configuration>
                     <source>1.5</source>
                     <target>1.5</target>
                     <showDeprecation>true</showDeprecation>
                     <showWarnings>true</showWarnings>
                     <compilerArgument>-Xlint:all,-serial,-unchecked</
compilerArgument>
                 </configuration>
             </plugin>


Regards,
Alan


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Re: Last SLP changes

by Alan.Cabrera :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On Oct 19, 2009, at 7:11 AM, Simone Bordet wrote:

> Hi,
>
> On Mon, Oct 19, 2009 at 16:06, Alan D. Cabrera <adc@...>  
> wrote:
>>
>> On Oct 19, 2009, at 6:04 AM, Simone Bordet wrote:
>>
>>> Hi,
>>>
>>> I have committed the changes I had locally to fix a bunch of bugs,
>>> among which the latest reported.
>>>
>>> Alan, I have also reorganized the poms: now all OSGi dependencies  
>>> are
>>> in the osgi module and not in the parent pom.
>>
>> Usually all of the dependencies versions for the whole project are  
>> in the
>> root pom.  But since these two modules are kinda orthogonal, in a  
>> way, it
>> seems ok to push the versions up.
>>
>> The a few, maybe only one, plugins in the build element are  
>> redundantly
>> repeated in the modules.
>
> Sorry don't follow...
> core does not depend on osgi, so I see no need to put in the root pom
> a dependency management for osgi, that's why I pushed it to the osgi
> module.
>
> Which are the repeated plugins ?


Something is busted w/ these POMs in that IntelliJ cannot load them up  
and create a project.  I'll look at this later today or, since you  
"busted" them, you could do that for me. (pretty please) :D


Regards,
Alan


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Re: Last SLP changes

by simonebordet :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

repeated plugins fixed.

IntelliJ 8.1.3 loads the pom fine.
Try to delete the idea files and then Open Project and choose the pom.xml.

Simon
--
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



Re: Last SLP changes

by Alan.Cabrera :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On Oct 19, 2009, at 7:50 AM, Simone Bordet wrote:

> Hi,
>
> repeated plugins fixed.
>
> IntelliJ 8.1.3 loads the pom fine.
> Try to delete the idea files and then Open Project and choose the  
> pom.xml.

Yeah, that's what I did.  However, it loads fine for me at work.  I'll  
delete my caches at home and see if that fixes it.


Regards,
Alan


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email