Re: Maven 3.0.3 generated different runtime classpath with the same POM

2012-01-31 Thread Sebastian Otaegui
Can you post your pom?

On Feb 1, 2012 1:15 AM, "Jörg Schaible"  wrote:
>
> Sebastian Otaegui wrote:
>
> > You can try doing 'mvn dependency:tree' to look at the artifact
resolution
> > tree with both versions.
>
> This does not help, since the plugin uses a dependency resolution
algorithm
> similar to M2.
>
> - Jörg
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>


Re: Maven 3.0.3 generated different runtime classpath with the same POM

2012-01-31 Thread Jörg Schaible
Sebastian Otaegui wrote:

> You can try doing 'mvn dependency:tree' to look at the artifact resolution
> tree with both versions.

This does not help, since the plugin uses a dependency resolution algorithm 
similar to M2.

- Jörg



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Noob question

2012-01-31 Thread Barrie Treloar
On Wed, Feb 1, 2012 at 10:15 AM, wimcolgate  wrote:
> I re-arranged things, the way I probably should have started.

The best advice I have seen is
"Don't fight against Maven, you'll loose. So, follow and use its
conventions, adopt its philosophy, use it the way it works. If Maven
doesn't work the way YOU want, don't use it.
http://stackoverflow.com/a/2254528/552958
(repeated on this list many time by others as well)

There is a reason that Maven has convention over configuration.
And as you have noticed, it's easier to conform to Maven and backport Ant :)

> The examples is now the main maven pom.xml. I indicate in my pom.xml, that
> have two modules, the utility class and the rest of the main library. These
> now all build into .class files.
>
> Next hurdle is to figure out how to build the examples. There are at least
> 11, and more will be forthcoming.
>
> The research I've done indicates maven's design center is a one jar/war per
> project; however, I did find this:
>
> http://stackoverflow.com/questions/2132958/ant-to-maven-multiple-build-targets
>
> Is this the proper path to follow?

It's not quite the same thing, but it is sound advice.

Chances are your configuration files and resources are going to be
identical amongst the examples, but as soon as they differ you will
have wished you split them into their own modules.
I'd recommend inserting another level into your build module named
"examples" so that your example projects are kept out of the way of
the main project and are easy to find.
i.e.
root/
  utilities/
  library/
  examples/
example-1/
example-2/
...
example-n/

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Maven 3.0.3 generated different runtime classpath with the same POM

2012-01-31 Thread Sebastian Otaegui
You can try doing 'mvn dependency:tree' to look at the artifact resolution
tree with both versions.


On Tue, Jan 31, 2012 at 10:57 AM, Julie Chi  wrote:

> I'm upgrading Maven from 2.2.1 to 3.0.3, it BUILD SUCCESS. However the
> runtime classpath(xxx.war \WEB-INF\lib)  are generated differently.  Ex. We
> defined  version 3.2.1.ga for hibernate-annotations, Maven2.2.1 generates
> version as it's defined 3.2.1.ga.jar.  However Maven 3.0.3  generated
> version 3.3.1.ga.jar and also a lot of more  jars  like titles-*.jar,
> spring-ldap-*.jar, ojdbc-14.jar  Those are not generated by Maven 2.2.1
> . I'm using the same POM , means the same version( 2.1.1) for
> maven-war-plugin.
>
> -Julie
>
>


-- 
Those who do not understand Unix are condemned to reinvent it, poorly.
Any sufficiently recent Microsoft OS contains an ad hoc,
informally-specified, bug-ridden, slow implementation of half of Unix.


Noob question

2012-01-31 Thread wimcolgate
Sorry for the remedial question. Noob here.

I am working in a java project that can be built using IntelliJ, Eclipse and
Ant; I want to add maven as an alternative.

I've modified pom.xml to override the defaults, and correctly locate the
sources for the main-line and tests. The directory structure is thus, not in
the default src/ test/ ... format. I can build the main src.

However, the original project also has a set of examples, as well as a
source utility (under a different package name) that is required by both the
test's and example's.

Is there a way to tweak my pom.xml to also build the examples, and reference
the utility source?

Thanks,

Wim

--
View this message in context: 
http://maven.40175.n5.nabble.com/Noob-question-tp5445807p5445807.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Maven 3.0.3 generated different runtime classpath with the same POM

2012-01-31 Thread Julie Chi
I'm upgrading Maven from 2.2.1 to 3.0.3, it BUILD SUCCESS. However the runtime 
classpath(xxx.war \WEB-INF\lib)  are generated differently.  Ex. We defined  
version 3.2.1.ga for hibernate-annotations, Maven2.2.1 generates version as 
it's defined 3.2.1.ga.jar.  However Maven 3.0.3  generated version 3.3.1.ga.jar 
and also a lot of more  jars  like titles-*.jar, spring-ldap-*.jar, 
ojdbc-14.jar  Those are not generated by Maven 2.2.1 . I'm using the same 
POM , means the same version( 2.1.1) for maven-war-plugin.

-Julie



Re: Noob question

2012-01-31 Thread wimcolgate
I re-arranged things, the way I probably should have started.

The examples is now the main maven pom.xml. I indicate in my pom.xml, that
have two modules, the utility class and the rest of the main library. These
now all build into .class files.

Next hurdle is to figure out how to build the examples. There are at least
11, and more will be forthcoming.

The research I've done indicates maven's design center is a one jar/war per
project; however, I did find this:

http://stackoverflow.com/questions/2132958/ant-to-maven-multiple-build-targets

Is this the proper path to follow?

Thanks,

Wim

--
View this message in context: 
http://maven.40175.n5.nabble.com/Noob-question-tp5445807p5446069.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: surefire report missing css, images

2012-01-31 Thread Barrie Treloar
On Tue, Jan 31, 2012 at 6:59 PM, Kristian Rosenvold
 wrote:
> I've been wondering about SUREFIRE-616; what is the "correct" way to
> actually fix this issue ?

I've been wondering what caused the breakage, but haven't had time to
find what changed.

I think the report secondary artefacts (like css, etc) need to be
built as part of the report generation.  I don't know if we know what
the mappings are but they can't be too hard to work out.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Spring context dependency not found..

2012-01-31 Thread Stephane-3
You were right. The class was not imported.

I add the statement:

import org.springframework.context.support.ClassPathXmlApplicationContext;

and the compilation passed fine.

What miss led me was that, under Eclipse, the maven dependencies for Spring
are not suggested.

Indeed, I installed the Maven plugin in the Eclipse Indigo from the Eclipse
Marketplace and when I do a right click on the project tree root and, under
the Maven contextual menu, do an Update Dependencies... the spring library
is not retrieved.

I do a mvn eclipse:eclipse beforehand as well.

Stephane

--
View this message in context: 
http://maven.40175.n5.nabble.com/Spring-context-dependency-not-found-tp5444070p5444213.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Spring context dependency not found..

2012-01-31 Thread Ansgar Konermann
Am 31.01.2012 10:28, schrieb Stephane-3:
> 
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Compilation failure
>
> /home/stephane/work/nki/dev/java/projects/springws/client/src/main/java/no/nki/springws/client/utils/Client.java:[25,2]
> cannot find symbol
> symbol  : class ClassPathXmlApplicationContext
> location: class no.nki.springws.client.utils.Client
>
> /home/stephane/work/nki/dev/java/projects/springws/client/src/main/java/no/nki/springws/client/utils/Client.java:[25,47]
> cannot find symbol
> symbol  : class ClassPathXmlApplicationContext
> location: class no.nki.springws.client.utils.Client

As you did not give the Client.java file's content, I can only speculate
about the actual reasons for this error message. The most likely reason:
you forgot to import ClassPathXmlApplicationContext.

If you'd like to get help quickly, make a copy of your project, erase
every file which is not strictly necessary to reproduce the compilation
error, and upload it to, say github. This will make it much easier for
potential list users to help you.

Kind regards

Ansgar

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: surefire report missing css, images

2012-01-31 Thread Kristian Rosenvold
I've been wondering about SUREFIRE-616; what is the "correct" way to 
actually fix this issue ?


Kristian

Den 31.01.2012 01:46, skrev Barrie Treloar:

On Tue, Jan 31, 2012 at 5:31 AM, Michael Norman
wrote:


  Running maven 3.0.4 via m2e (Maven Integration for Eclipse version
1.0.100.20110804-1717).


Google will tell you (
https://www.google.com/search?q=surefire+report+missing+css) that its a
known issue http://jira.codehaus.org/browse/SUREFIRE-616.

The work around is to run "site" so that the css/images get generated.
But dont run "clean" or they will get removed again.

Some people also claim you can downgrade your surefire-report plugin
version to 2.4.2and it works again (others have tried and it didn't work
for them).

If you're feeling adventurous a patch to fix this would be appreciated.




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org