building for 1.4 and 1.6

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

building for 1.4 and 1.6

Andrew Hamilton-4

Users,

 

I’m approaching a project by thinking to build it for 1.4 and for 1.6.

How have your experiences been for these approaches of compiling for source 1.4 and source 1.6?

I’m familiar with the syntax in the POM’s, but I’m always curious as to what caveats lay behind the scenes, so I wanted to ask if people had positive or negative experiences with that.

 

I’m on Maven 2.2.0 and 1.6.0_17.  I use the m2e Eclipse plugin for some thing, but find the command line to be more thorough and more reliable.

 

Thanks in advance,

Andrew

Reply | Threaded
Open this post in threaded view
|

Re: building for 1.4 and 1.6

justinedelson
I think this would be better suited to the Maven mailing list, but...

the answer depends upon what you are trying to accomplish. If you are
talking about retroweaving, I would advise you to avoid it. Although it
is reasonably simple to produce a retrowoven JAR file with Maven, you
will run into trouble using the retrowoven JAR as a dependency more than
one level down because Maven only allows a single set of dependencies
per project.



On 7/28/10 12:27 PM, Andrew Hamilton wrote:

> Users,
>
>  
>
> I’m approaching a project by thinking to build it for 1.4 and for 1.6.
>
> How have your experiences been for these approaches of compiling for
> source 1.4 and source 1.6?
>
> I’m familiar with the syntax in the POM’s, but I’m always curious as to
> what caveats lay behind the scenes, so I wanted to ask if people had
> positive or negative experiences with that.
>
>  
>
> I’m on Maven 2.2.0 and 1.6.0_17.  I use the m2e Eclipse plugin for some
> thing, but find the command line to be more thorough and more reliable.
>
>  
>
> Thanks in advance,
>
> Andrew
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]