Re: Aspect J

[Martijn Dashorst]

http://stackoverflow.com/questions/12423965/maven-aspectj-all-steps-to-configure-it

On Mon, Oct 12, 2015 at 12:04 PM, aalok singhvi  wrote:
> Hello,
>
> I have a present ant project which compiles...classes using
>
> javac first and than compiles using iajc .
>
> How can i do similar stuff in maven.
>
> Thanks
>
>
> --
> Aalok Singhvi



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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

Central search is empty

[Martijn Dashorst]

It appears that the Maven central search index (search.maven.org) was
not able to load the index as any search now returns an empty response
(no entries found).

Martijn

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

Profile vs toolchains: javadoc -Xdoclint:none

[Martijn Dashorst]

In our master POM we have defined the following (logical) profile to
disable the doclint of javadoc to be able to actually render our
javadocs.


Java 8

1.8



-Xdoclint:none



However this parameter is not supported by Java 7 and anyone trying to
use this parameter with Java 7 will get an error. Now this is not a
problem you'd think, since this is only active when you run Maven with
Java 8? Right?

Well, the truth is more complicated when you use maven toolchains...
In our case we have created a release profile with the toolchains
plugin configured to actually use Java 7. So Maven runs with Java 8,
enables the "Java 8" profile, adds the "additionalparam" configuration
to the javadoc plugin, and starts the toolchain... with java 7's
javadoc, giving a big error.

Does a solution exist for this problem? (granted we can run the build
using Java 7, but that is exactly what I was trying to avoid with the
toolchains!)

Martijn

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

Re: Where's the new home for the clirr-maven-plugin?

[Martijn Dashorst]

It appears to work like a charm. Thanks!

Martijn

On Mon, Jun 8, 2015 at 7:44 AM, Karl Heinz Marbaise  wrote:
> Hi Thomas,
>
> On 6/8/15 12:47 AM, Thomas Broyer wrote:
>>
>> https://github.com/mojohaus/clirr-maven-plugin ?
>
>
> Should be accessed via:
>
> http://www.mojohaus.org/clirr-maven-plugin/
>
> If not the documentation has not been regenerated yet..
> will happen during the next days...
>
> Kind regards
> Karl Heinz Marbaise
>>
>>
>>
>> On Mon, Jun 8, 2015 at 12:26 AM Martijn Dashorst
>> 
>> wrote:
>>
>>> The clirr-maven-plugin was one of the unfortunate casualties of
>>> codehaus' demise.
>>>
>>> It should get a new home, but my google-fu leaves me without any
>>> results. Where does this plugin live on?
>>>
>>> Martijn
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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

Re: Where's the new home for the clirr-maven-plugin?

[Martijn Dashorst]

OK, thanks!

It appears that the project was migrated, but not its site. Is that as
simple as running a mvn site, and copying target/site to a ghpages
branch?

Martijn


On Mon, Jun 8, 2015 at 9:24 AM, Baptiste Mathus  wrote:
> Yes, MOJO@Codehaus project was renamed MojoHaus.
>
> So, basically, any project you found docs for under
> http://mojo.codehaus.org/xyz-maven-plugin should follow the following
> pattern:
>
>- its sources should be found under
>https://github.com/mojohaus/xyz-maven-plugin
>- its website should be found under
>http://www.mojohaus.org/xyz-maven-plugin/
>
> If not, then that plugin may have been NOT migrated (for various reasons,
> but at least temporary lack of interest from maintainers). If you need
> them, please ping us on our ML
> (information about it will be updated under http://www.mojohaus.org in the
> upcoming days & weeks).
>
> Cheers
>
> 2015-06-08 0:47 GMT+02:00 Thomas Broyer :
>
>> https://github.com/mojohaus/clirr-maven-plugin ?
>>
>>
>> On Mon, Jun 8, 2015 at 12:26 AM Martijn Dashorst <
>> martijn.dasho...@gmail.com>
>> wrote:
>>
>> > The clirr-maven-plugin was one of the unfortunate casualties of
>> > codehaus' demise.
>> >
>> > It should get a new home, but my google-fu leaves me without any
>> > results. Where does this plugin live on?
>> >
>> > Martijn
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: users-h...@maven.apache.org
>> >
>> >
>>
>
>
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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

Where's the new home for the clirr-maven-plugin?

[Martijn Dashorst]

The clirr-maven-plugin was one of the unfortunate casualties of
codehaus' demise.

It should get a new home, but my google-fu leaves me without any
results. Where does this plugin live on?

Martijn

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

Re: [VOTE] Name our mascot: "Shotgun" vs "The Maven Owl"

[Martijn Dashorst]

B

Martijn

On Mon, Dec 15, 2014 at 2:27 PM, David Hoffer  wrote:
> B
>
> -Dave
>
> On Mon, Dec 15, 2014 at 6:22 AM,  wrote:
>>
>> B
>>
>> Cody Fyler
>> Lending Grid Build Team
>> G=Lending Grid Builds
>> (515) – 441 - 0814
>>
>> -Original Message-
>> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
>> Sent: Monday, December 15, 2014 4:39 AM
>> To: Maven Users List; Maven Developers List
>> Subject: [VOTE] Name our mascot: "Shotgun" vs "The Maven Owl"
>>
>> After the run-off round, we are left with two names standing.
>>
>> This second vote will be a straight and simple majority wins.
>>
>> The vote will be open for at least 72 hours (with the potential of an
>> extension until I send a message saying that the polls are closed)
>>
>> There will be no discussion in this thread, we have talked it all enough
>> already. If you want to discuss something, please use a different thread.
>>
>> Vote:
>>
>> [A]: Shotgun
>> [B]: The Maven Owl
>>
>> Thank you very much for your time
>>
>> -Stephen
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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

Re: Unable to use the maven-release-plugin to release

[Martijn Dashorst]

To fix this I had to add



org.apache.maven.scm
maven-scm-provider-gitexe
1.9



to the plugin definition of the m-r-p (version 2.4.1).

Martijn



On Wed, Feb 5, 2014 at 5:44 PM, Martijn Dashorst  wrote:

> This is still an issue. Can someone please fix the maven-release-plugin to
> work with a decent version of git?
>
> Martijn
>
>
> On Sat, Dec 28, 2013 at 4:22 PM, Robert Scholte wrote:
>
>> Hi,
>>
>> it depends on the type of problem you're facing.
>>
>> as said before, these are probably the best options:
>>
>> - try maven-release-plugin 2.4
>> - use an older version of GIT with English locale.
>>
>> For details see https://jira.codehaus.org/browse/MRELEASE-812
>>
>> Robert
>>
>> Op Sat, 28 Dec 2013 15:34:26 +0100 schreef Julien Nicoulaud <
>> julien.nicoul...@gmail.com>:
>>
>>
>>  Hi,
>>>
>>> I tried the workaround (release plugin 2.4.2 + maven-scm-provider-gitexe
>>> 1.8.1) without success, still messing up releases with snapshot versions.
>>> I'm on git 1.8.5.2.
>>>
>>> Am I missing something else ?
>>> Here is my parent pom with the release profile I use if this can help:
>>> https://gitorious.org/net-ju-n-parent-pom/net-ju-n-parent-pom
>>>
>>> Cheers
>>>
>>>
>>> 2013/12/26 Mark Derricutt 
>>>
>>>  You're correct - 1.8.1 is not related to Git 1.8, however it is the
>>>> latest
>>>> release - and a fix that SUPPORTS Git 1.8 was actually released back in
>>>> something like scm-provider 1.5 earlier in the year - only the Maven
>>>> Release Plugin DOES NOT USE IT.
>>>>
>>>> We should really have a new release of m-r-p that forces the use of
>>>> current scm-providers cause I can see this problem only increasing as
>>>> more
>>>> people a) upgrade git or b) move to git and get pissed off with
>>>> maven+git
>>>>
>>>> This work around works, but really - goes against convention over
>>>> configuration.
>>>>
>>>>
>>>> On 27 Dec 2013, at 1:43, Robert Scholte wrote:
>>>>
>>>> > I don't think this will fix the issue.
>>>> >
>>>> > SCM 1.8.1[1] is not related to GIT 1.8.x
>>>> >
>>>> > It's a coincidence that the most recent version of SVN, GIT and SCM
>>>> are
>>>> all 1.8.x
>>>> >
>>>> > Robert
>>>>
>>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

Re: Unable to use the maven-release-plugin to release

[Martijn Dashorst]

This is still an issue. Can someone please fix the maven-release-plugin to
work with a decent version of git?

Martijn


On Sat, Dec 28, 2013 at 4:22 PM, Robert Scholte wrote:

> Hi,
>
> it depends on the type of problem you're facing.
>
> as said before, these are probably the best options:
>
> - try maven-release-plugin 2.4
> - use an older version of GIT with English locale.
>
> For details see https://jira.codehaus.org/browse/MRELEASE-812
>
> Robert
>
> Op Sat, 28 Dec 2013 15:34:26 +0100 schreef Julien Nicoulaud <
> julien.nicoul...@gmail.com>:
>
>
>  Hi,
>>
>> I tried the workaround (release plugin 2.4.2 + maven-scm-provider-gitexe
>> 1.8.1) without success, still messing up releases with snapshot versions.
>> I'm on git 1.8.5.2.
>>
>> Am I missing something else ?
>> Here is my parent pom with the release profile I use if this can help:
>> https://gitorious.org/net-ju-n-parent-pom/net-ju-n-parent-pom
>>
>> Cheers
>>
>>
>> 2013/12/26 Mark Derricutt 
>>
>>  You're correct - 1.8.1 is not related to Git 1.8, however it is the
>>> latest
>>> release - and a fix that SUPPORTS Git 1.8 was actually released back in
>>> something like scm-provider 1.5 earlier in the year - only the Maven
>>> Release Plugin DOES NOT USE IT.
>>>
>>> We should really have a new release of m-r-p that forces the use of
>>> current scm-providers cause I can see this problem only increasing as
>>> more
>>> people a) upgrade git or b) move to git and get pissed off with maven+git
>>>
>>> This work around works, but really - goes against convention over
>>> configuration.
>>>
>>>
>>> On 27 Dec 2013, at 1:43, Robert Scholte wrote:
>>>
>>> > I don't think this will fix the issue.
>>> >
>>> > SCM 1.8.1[1] is not related to GIT 1.8.x
>>> >
>>> > It's a coincidence that the most recent version of SVN, GIT and SCM are
>>> all 1.8.x
>>> >
>>> > Robert
>>>
>>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

Release plugin 2.4.2 ignores pushChanges=false

[Martijn Dashorst]

Is it me or does the maven-release-plugin ignore the pushChanges setting?

Running the release process actually pushes the changes to the git
repo. And I *really* don't want that to happen.

Relevant configuration:


org.apache.maven.plugins
maven-release-plugin
2.4.2
true

false
wicket-@{project.version}
false




$ git --version
git version 1.8.5.2

$ mvn --version
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a;
2013-09-17 17:22:22+0200)
Maven home: /usr/local/Cellar/maven/3.1.1/libexec
Java version: 1.7.0_45, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.9.1", arch: "x86_64", family: "mac"

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

Unable to use the maven-release-plugin to release

[Martijn Dashorst]

I'm currently in week 4 of trying to release Apache Wicket and I am giving up.

The release plugin fails to tag the updated release poms but instead
tags the SNAPSHOT version. Then the release plugin starts to release
the tag which unfortunately points to the SNAPSHOT version.

My best guess is that Maven fails to commit the updated release poms
and continues to tag and release the 6.13.0-SNAPSHOT versions.

I have upgraded to maven 3.1.1, the release plugin runs at 2.4.2 and
our specified configuration is:


org.apache.maven.plugins
maven-release-plugin
2.4.2
true

false
wicket-@{project.version}
false



When merged with the Apache parent pom (v10), this results in:


maven-release-plugin
2.4.2
true

false
wicket-@{project.version}
false
false
deploy
-Papache-release



A couple of observations: up til our 6.12.0 release, the process
worked without a glitch. Since then I got a new laptop and have
migrated all settings to my new box.

I have tried to revert to maven-release-plugin:2.3.2 (the 6.12.0
release was baked with this one), I have tried to apply apache-parent
pom v13, and both failed with the same result.

I am currently at a loss...

Does anyone have a solution?

Thanks,

Martijn

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

Re: wicket is secure by default. why use spring security?

[Martijn Dashorst]

The default auth-roles project is just an example of how to do
*simple* authentication and authorization. It only supports 3 roles:
not logged in, logged in user and administrator. For more complex
things or flexibility you'll need something like Apache Shiro, Wicket
Security (now hosted on wicket stuff), or spring security.

Some applications are a hybrid of old Spring MVC pages/insert other
framework that use [spring security|shiro]. Migrating those
applications to Wicket could leave the old pages alive, using the
spring security stuff.

Wicket being secure by default is different from having an
authorization/authentication scheme out of the box. Security
frameworks are just as encompassing as ORM frameworks. Java comes with
JDBC, so why use Hibernate?

Martijn

On Mon, Sep 19, 2011 at 9:55 AM, Zilvinas Vilutis  wrote:
> Hi all Wicket users.
>
> While I was trying to design a wicket app in my mind - the first thing
> I thought of was authentication and ( spring ) security.
>
> I know that "wicket is secure" by default ( a quote from wicket
> features? :), we can use wicket auth & annotation based security.
> Wicket will automatically redirect to original page after login.
>
> So...did anyone think of it - what is the real reason to use spring or
> other security framework ( shiro? ) for authentication? what benefits
> does it bring apart from some standards & overhead for the app? is it
> integration with other auth systems ( OpenID, Facebook login or
> whatever )? or what?
>
> Just pennies for thought...
>
> Žilvinas Vilutis
>
> Mobile:   (+1) 623 330 6048
> E-mail:   cika...@gmail.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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

Re: M3 fails to download parent pom

[Martijn Dashorst]

Here's the contents of settings.xml relevant to our repo manager:



our-repository
Maven Repository Manager running on 
corp.com
http://repo.corp.com/artifactory/repo
*



Martijn

On Wed, Nov 10, 2010 at 2:33 PM, Stephen Connolly
 wrote:
> How have you defined your corp maven repo in your settings.xml
>
> I'm wondering if it's a bug in maven 2 pulling releases from the wrong repo
> and therefore you don't notice that the repo is defined incorrectly in
> settings.xml
>
> On 10 Nov 2010 08:39, "mjsell"  wrote:
>
>
> Yeah, this is definitely not a pom that exists in the project tree, so the
> parent-pom resolution changes mentioned in the compatibility notes do not
> apply.  In my case it is a corporate pom that is separately released, and
> all of our project trees end up inheriting from a previously released
> version of it.  Maven 2.2.1 successfully pulls it down from the remote
> repository, but Maven 3.0 does not.  If it is in the local repository
> everything works fine, but if it needs to be retrieved from the remote
> repository then it just fails without trying.  Interestingly, if I change it
> to a snapshot version of the corporate pom, then Maven 3 appears to
> correctly attempt to pull it from the remote repositories.  This definitely
> sounds like a bug to me.
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/M3-fails-to-download-parent-pom-tp3240199p3258005.html
>
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---...
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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

Re: M3 fails to download parent pom

[Martijn Dashorst]

Yes, and that doesn't describe our case.

Company wide parent pom, similar to the ASF parent pom. is a separate
svn project, not linked from any reactor.

Project specific parent pom with submodules. Project parent pom
extends company wide parent pom.

New release of company wide parent pom : going from version 1 to version 2.

Project specific parent pom adjusts version for company wide parent
pom from 1 to 2.

Maven 3 fails to build: it doesn't download version 2 of company wide
parent pom.

Martijn

On Tue, Nov 9, 2010 at 3:12 PM, MK Tan  wrote:
> Have you go through
> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ParentPOMResolution
>
> On Nov 9, 2010 4:37 PM, "mjsell"  wrote:
>>
>> I ran into this today when trying to move to Maven 3.. any news? Has a
>> ticket been written?
>> --
>> View this message in context:
> http://maven.40175.n5.nabble.com/M3-fails-to-download-parent-pom-tp3240199p3256007.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
>>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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

Re: adding java sources to classpath with maven-eclipse-plugin

[Martijn Dashorst]

add an include pattern. Default maven filters out java files.

Martijn

On Sun, Nov 7, 2010 at 11:26 AM, James Ring  wrote:
> (Please CC me on replies, I am not subscribed to this list)
>
> Hi there,
>
> I have a GWT project which programatically starts a DevMode shell. The
> problem I have is that GWT needs access to the Java source code in the
> classpath at runtime. I have tried adding my src/main/java directory
> to the resources list (in the following snippet), but this doesn't
> seem to have the desired effect.
>
> 
>  
>    
>      src/main/java
>    
>  
>  ...
> 
>
> Basically the following code should not throw an exception when run as
> an Eclipse JUnit test.
>
> classLoader.getResource("com/mycompany/mypackage/client/MainPage.java")
>
> The test passes when running mvn test, but when running it inside an
> Eclipse project generated with "mvn eclipse:eclipse", it fails
> (resource not found). As a workaround I just add the src/main/java
> directory to the runtime classpath and then GWT is happy and I'm
> happy. :)
>
> $ mvn -version
> Apache Maven 2.2.1 (r801777; 2009-08-07 05:16:01+1000)
> Java version: 1.6.0_22
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x" version: "10.5.8" arch: "x86_64" Family: "mac"
>
> Using org.apache.maven.plugins:maven-eclipse-plugin:2.7.
>
> Thanks for your help!
>
> Regards,
> James
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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

Re: maven-eclipse-plugin Does not resolve workspace project name

[Martijn Dashorst]

On Thu, Oct 28, 2010 at 2:54 PM, Ron Wheeler
 wrote:
> It is hard to get enthusiastic about maintaining old software that has been
> replaced by better stuff that is free.

maven-eclipse-plugin works roughly 100% of the time here, but the
m2eclipse plugin fails miserably with our maven project setup. And yes
we tried the latest version. It always results in having to download
and install vanilla eclipse.

> Get Eclipse/STS and you have a much more current supported set of code and
> everything that you need to develop with Maven.

Meh. sounds like having a commercial stake in the project. I happen to
like commandline mvn eclipse:eclipse without having to bloat my
eclipse installation with unnecessary plugins—eclipse has trouble
enough keeping up with the size of our projects.

> You can also get training and commercial level support if you want it.
> Why would anyone want to invest in older technology?

Why is it older? Because you don't like command line tools? Happening
to like command line tools make someone a dinosaur?
Is the maven-eclipse-plugin old because it is not given any resources
by sonatype which happens to maintain the m2eclipse plugin?

Why bother with building a release for maven at all? Doesn't m2eclipse
supplant that too?

Martijn

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

M3 fails to download parent pom

[Martijn Dashorst]

Is this a known issue?

A new company parent pom release was not downloaded by maven 3, and
hence failed to do anything with my project. Running maven 2.2.1 on
the project successfully downloaded the parent pom.

Running maven 3 gave the following output:

$ mvn -X help:effective-pom
Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x" version: "10.6.4" arch: "x86_64" Family: "mac"
[INFO] Error stacktraces are turned on.
[DEBUG] Reading user settings from /Users/dashorst/.m2/settings.xml
[DEBUG] Reading global settings from /usr/share/maven/conf/settings.xml
[DEBUG] Using local repository at /Users/dashorst/.m2/repository
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Could not find artifact
nl.topicus.onderwijs:onderwijs-project-parent:pom:1.3 and
'parent.relativePath' points at wrong local POM @ line 4, column 10

at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:325)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:607)
at 
org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:556)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:228)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
[ERROR]
[ERROR]   The project nl.topicus.eduarte:eduarte:2.06-SNAPSHOT
(/Users/dashorst/Workspaces/eduarte/eduarte/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact
nl.topicus.onderwijs:onderwijs-project-parent:pom:1.3 and
'parent.relativePath' points at wrong local POM @ line 4, column 10 ->
[Help 2]
org.apache.maven.model.resolution.UnresolvableModelException: Could
not find artifact
nl.topicus.onderwijs:onderwijs-project-parent:pom:1.3
at 
org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:183)
at 
org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:819)
at 
org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:670)
at 
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:308)
at 
org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:354)
at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:305)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:607)
at 
org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:556)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:228)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException:
Could not find artifact
nl.topicus.onderwijs:o

Re: maven-eclipse-plugin Does not resolve workspace project name

[Martijn Dashorst]

So how does one get ownership of the plugin? I've contributed 2
patches with an implied promise that they would be included when the
failing ITs on Barrie's workspace were resolved. Unfortunately that is
the last of it.

Why the constant commercials for the m2eclipse plugin? Instead why not
ask for some interested developer to take over the
maven-eclipse-plugin? Isn't this an open source community?

Martijn

On Wed, Oct 27, 2010 at 7:28 PM, Wayne Fay  wrote:
>> When I run eclipse:eclipse the project name in the .project file will be the
>> artifactId (by default) despite the eclipse project name being something
>> different.
>
> Yes, this is how m-e-p works. The .project file is overwritten by
> m-e-p and so you will lose all settings that you set up in Eclipse
> unless you also set them up in your pom via configuration:
> http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
>
>> This causes a problem when eclipse tries to build new projects workspace
>> because the eclipse workspace project is one thing and the .project's
>> project is something completely different.
>
> This is not m-e-p's problem. Stop renaming your projects if you want
> to use m-e-p and use it to regenerate the .project files. Keep the
> name as the artifactId, or change the artifactId in the pom to meet
> your needs.
>
>> How come the maven-eclipse-plugin will never resolve the workspace project
>> name to the .project project name.  Or even offer a flag like
>> true to override the original
>> functionality?
>
> In the last 180 days, there have been zero issues in MECLIPSE resolved.
> At the same time, 40 have been updated and 20 were created.
> http://jira.codehaus.org/browse/MECLIPSE
>
> For all intents, m-e-p is dead. If you require this functionality,
> feel free to hack the plugin to add it and donate your changes back to
> be included in a future release -- but bear in mind there may never be
> another release. The last release was Feb 23, 2010 and before that was
> June 13, 2009.
>
> I suggest upgrading to m2eclipse:
> http://m2eclipse.sonatype.org/
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

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

Re: maven-eclipse-plugin and POM packaging projects

[Martijn Dashorst]

On Tue, Jun 15, 2010 at 12:04 PM, Daniele Dellafiore  wrote:
> I have "patched" maven-eclipse-plugin to create an eclipse project also for
> projects with "pom" packaging type.
> I was wondering if this was a bug or a feature and if someone is interested
> in the plugin behaving this way other than me.

I am glad the pom packaging projects don't generate .project files
anymore. It was a drag with importing multimodule projects in eclipse.
Far more easy to get all non-pom projects in one go, and just add the
three pom type projects.

My €0.02 (which isn't that much worth nowadays)

Martijn

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

Re: The plugin 'org.apache.com.plugins:maven-eclipse-plugin' does not exist or no valid version could be found

[Martijn Dashorst]

try groupid: org.apache.maven.plugins instead

Martijn

On Sat, Nov 28, 2009 at 8:24 PM, Hannelore Brijs
 wrote:
>
> MessageI have installed
> m2eclipse, and tried to execute this command: mvn
> eclipse:eclipse
> Then I got this
> error: The plugin 'org.apache.com.plugins:maven-eclipse-plugin' does not exist
> or no valid version could be found
> What is
> wrong?
> _
> De nieuwe Windows 7: vind de juiste pc voor jou. Meer informatie.
> http://windows.microsoft.com/shop



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0

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

Re: Downloads link doesn't work

[Martijn Dashorst]

On Mon, Aug 17, 2009 at 3:37 PM, Wendy Smoak wrote:
> Can you try a different browser?  I believe it's a known issue with
> Safari.  For example, ServiceMix has a note on their download page
> about it.  http://servicemix.apache.org/servicemix-323.html

I don't use ff for daily usage :)

With Wicket we use a different strategy: we link to a directory
containing our distributables, instead of the artifact itself:

http://wicket.apache.org/getting-wicket.html

has a link to:

http://www.apache.org/dyn/closer.cgi/wicket/1.4.0

which contains (on mirrors):

 Parent Directory   27-Jul-2009 17:36  -
 KEYS   23-Jul-2009 19:5715k
 apache-wicket-1.4.0.tar.gz 23-Jul-2009 20:09  21.4M
 apache-wicket-1.4.0.tar.gz.asc 23-Jul-2009 20:09 1k
 apache-wicket-1.4.0.zip23-Jul-2009 20:04  29.5M
 apache-wicket-1.4.0.zip.asc23-Jul-2009 19:57 1k

Still a 3 click download, but better than the hoops I had to jump
through to get at the Maven distribution due to my browser bug.

Martijn

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

Downloads link doesn't work

[Martijn Dashorst]

The page http://maven.apache.org/download.html provides links to the
mirroring system, but it seems to be configured wrongly. When I click
on the link to e.g.
http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-2.2.1-bin.tar.gz
I get the mirrors page downloaded as if it were the tarball (i.e. a
5kb file instead of a 1.5MB file).

Going to http://www.apache.org/dyn/closer.cgi/maven/binaries/,
selecting a download mirror and downloading the tarball does work
though.

I'm using safari 4.0.2

Martijn

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

Re: Maven java.lang.OutOfMemoryError

[Martijn Dashorst]

I think you need to fork the compiler. See
http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-with-memory-enhancements.html

Martijn

On Thu, Aug 13, 2009 at 12:26 PM, kopemor wrote:
>
> Hello,
>
> I am getting "java.lang.OutOfMemoryError: Java heap space" exception when I
> compile my project using Maven. I have tried several options:
>
> 1. Setting variable: export MAVEN_OPT=-Xmx1024m
>
> 2. Using Maven compile plugin:
>     
>       org.apache.maven.plugins
>        maven-compiler-plugin
>        
>          1.5
>          1.5
>          UTF-8
>          -Xms512m
>          -Xmx1024m
>          true
>        
>      
>
> I have even tried to put max heap size to 4094, the result is the same.
>
> Any help?
>
> --
> View this message in context: 
> http://www.nabble.com/Maven-java.lang.OutOfMemoryError-tp24952498p24952498.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
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0

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

Re: Maven 1.0.2 Errors

[Martijn Dashorst]

Not sure how you compare things in your assertions, but it may be
someone in your team who has different svn client settings (EOL style)
or not the correct encoding for the files. This is a certain way to
get strange test results. Write the comparison strings to a file and
open it with a hex editor to see the contents. Do this also on other
failing platforms to see if there's a difference.

Martijn

On Thu, Jul 9, 2009 at 6:53 AM, Dunstall,
Christopher wrote:
> Hi,
>
> Lately, I've been getting some really bizarre behaviour from running junit 
> tests in Maven 1.0.2.
>
> The tests were written in Eclipse, where they run fine.  However, when I run 
> a maven target, it runs the junit test but shows an error.  As a result, it 
> finishes up as the build has failed.
>
>    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.74 sec
>    [junit] Running au.edu.csu.ole.msi.impl.dao.test.WebMethodsTest
> Service: webmethods:pMDRTarget.flowservices:getCampusName?campusCode=A
> webmethods
> msi.flowservices
> getOutlineInfo
> webmethods
> msi.flowservices
> getOutlineInfo
>    [junit] Tests run: 6, Failures: 0, Errors: 5, Time elapsed: 0.808 sec
>    [junit] [ERROR] TEST au.edu.csu.ole.msi.impl.dao.test.WebMethodsTest FAILED
>
> You can see here that it output the information from the test as I expected, 
> but still had 'errors'.  Running the Stacktrace or verbose switch with maven 
> reveals absolutely nothing.
>
> To add even a more bizarre twist to it, some tests run fine with no errors on 
> my Macbook Pro, but on my colleagues Windows box it errors.
>
> More concering is that our continuum install also gets the errors (on a Unix 
> VM), and running the -Dmaven.test.failure.ignore=true switch isn't possible 
> to my knowledge.
>
> Has anyone seen this before or know what the problem is, it really is driving 
> me batty. :(
>
> Thanks,
>
> Chris Dunstall | Service Support - Applications
> Technology Integration/OLE Virtual Team
> Division of Information Technology | Charles Sturt University | Bathurst, NSW
>
> Ph: 02 63384818 | Fax: 02 63384181
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: eclipse plugin 2.7: link project instead of repository jar

[Martijn Dashorst]

This is not the functionality I described. What you describe already
works in 2.5, as it is the multimodule functionality. What I described
is that you can check out Wicket into your workspace, and start
hacking on your own Wicket application, where the
maven-eclipse-plugin:2.7 will find the wicket projects and link them
as a project instead of a jar dependency.

i.e.:

workspace/wicket/wicket
workspace/wicket/wicket-extensions
workspace/wicket/wicket-spring
workspace/mywicketapp

This become workspace projects like:

wicket
wicket-extensions
wicket-spring
mywicketapp

and if mywicketapp depends on wicket and wicket-spring, those will
become project dependencies instead of jar dependencies. No need for a
single parent, no need for a root pom to get this to work.

Martijn

On Wed, Jun 17, 2009 at 10:35 PM, Jim Sellers wrote:
> I've found that it only works if your other projects:
> 1) have the same parent and you run the maven command from the parent
>
> 2) the other project is at the top level of your workspace.  e.g.
> MyWonderfulProject
> \ pom.xml
>
> MyMasterLib
> \ pom
> \ MySubModuleLib
>  \ pom.xml
>
> From MyWonderfulProject, if you have a dependency on MySubModuleLib, it
> doesn't seem to link it.  If you like to MyMaterLib, it would.
>
> HTH
> Jim
>
>
> On Wed, Jun 17, 2009 at 12:25 PM, Daniele Dellafiore wrote:
>
>> Hi everyone.
>>
>> I read here:
>> http://martijndashorst.com/blog/2009/05/29/maven-eclipse-plugin-woes-fixed/
>>
>> that eclipse maven plugin 2.7 has a new feature such as "such as
>> searching your workspace for projects that are snapshot dependencies,
>> and adding a project link instead of a jar dependency.".
>> How is that supposed to work?
>>
>> I have a project A that uses B-1.0-SNAPSHOT but the mvn
>> eclipse:eclipse still links the jar.
>> There is some configuration to do?
>>
>> thanks!
>>
>> --
>> Daniele Dellafiore
>> http://blog.ildella.net
>> http://twitter.com/ildella
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

We also tested it with an AspectJ project, and that works as well.

Martijn

On Fri, May 29, 2009 at 10:09 AM, Martijn Dashorst
 wrote:
> Works great! Thanks Barrie!!!
>
> Here's the log entry for my run:
>
> macbookpro:myproject dashorst$ mvn eclipse:eclipse
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'eclipse'.
> Downloading: 
> http://repository/artifactory/repo/org/apache/maven/plugins/maven-eclipse-plugin/2.7-SNAPSHOT/maven-eclipse-plugin-2.7-20090529.071922-5.pom
> 9K downloaded
> Downloading: 
> http://repository/artifactory/repo/org/apache/maven/plugins/maven-eclipse-plugin/2.7-SNAPSHOT/maven-eclipse-plugin-2.7-20090529.071922-5.jar
> 203K downloaded
> [INFO] 
> 
> [INFO] Building quickstart
> [INFO]    task-segment: [eclipse:eclipse]
> [INFO] 
> 
> [INFO] Preparing eclipse:eclipse
> [INFO] snapshot org.mortbay.jetty:maven-jetty-plugin:6.1-SNAPSHOT:
> checking for updates from topicus-plugin-snapshot-repository
> [INFO] snapshot org.mortbay.jetty:project:6.1-SNAPSHOT: checking for
> updates from topicus-plugin-snapshot-repository
> [INFO] No goals needed for project - skipping
> [WARNING] Attempting to build MavenProject instance for Artifact
> (org.apache.maven.plugins:maven-eclipse-plugin:2.7-20090529.071922-5)
> of type: maven-plugin; constructing POM artifact instead.
> [INFO] [eclipse:eclipse]
> [INFO] Using Eclipse Workspace: /Workspaces/eduarte
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
> [WARNING] Workspace defines a VM that does not contain a valid
> jre/lib/rt.jar:
> /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
> [INFO] Adding default classpath container:
> org.eclipse.jdt.launching.JRE_CONTAINER
> [INFO] Resource directory's path matches an existing source directory.
> Resources will be merged with the source directory src/main/java
> [INFO] Resource directory's path matches an existing source directory.
> Resources will be merged with the source directory src/test/java
> [INFO] Not writing settings - defaults suffice
> [INFO] Wrote Eclipse project for "myproject" to /Workspaces/eduarte/myproject.
> [INFO]
>       Javadoc for some artifacts is not available.
>       Please run the same goal with the -DdownloadJavadocs=true
> parameter in order to check remote repositories for javadoc.
>       List of artifacts without a javadoc archive:
>         o junit:junit:3.8.2
>         o log4j:log4j:1.2.14
>         o org.slf4j:slf4j-api:1.4.2
>         o org.mortbay.jetty:jetty:6.1.4
>         o org.mortbay.jetty:jetty-util:6.1.4
>         o org.mortbay.jetty:servlet-api-2.5:6.1.4
>         o org.mortbay.jetty:jetty-management:6.1.4
>         o mx4j:mx4j:3.0.1
>         o mx4j:mx4j-tools:3.0.1
>         o org.slf4j:slf4j-log4j12:1.4.2
>
> [INFO] 
> 
> [INFO] BUILD SUCCESSFUL
> [INFO] 
> 
> [INFO] Total time: 18 seconds
> [INFO] Finished at: Fri May 29 10:06:15 CEST 2009
> [INFO] Final Memory: 9M/16M
> [INFO] 
> 
>
>
> On Fri, May 29, 2009 at 9:20 AM, Arnaud HERITIER  wrote:
>> I just deployed it in the snapshots repo. It's numbered
>> : 2.7-20090529.071922-5Thx for your hard work Barrie.
>> Cheers
>>
>>
>> Arnaud
>>
>>
>> On Fri, May 29, 2009 at 6:05 AM, Barrie Treloar  wrote:
>>
>>> On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
>>>  wrote:
>>> > On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar 
>>> wrote:
>>> >> I went

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

Works great! Thanks Barrie!!!

Here's the log entry for my run:

macbookpro:myproject dashorst$ mvn eclipse:eclipse
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
Downloading: 
http://repository/artifactory/repo/org/apache/maven/plugins/maven-eclipse-plugin/2.7-SNAPSHOT/maven-eclipse-plugin-2.7-20090529.071922-5.pom
9K downloaded
Downloading: 
http://repository/artifactory/repo/org/apache/maven/plugins/maven-eclipse-plugin/2.7-SNAPSHOT/maven-eclipse-plugin-2.7-20090529.071922-5.jar
203K downloaded
[INFO] 
[INFO] Building quickstart
[INFO]task-segment: [eclipse:eclipse]
[INFO] 
[INFO] Preparing eclipse:eclipse
[INFO] snapshot org.mortbay.jetty:maven-jetty-plugin:6.1-SNAPSHOT:
checking for updates from topicus-plugin-snapshot-repository
[INFO] snapshot org.mortbay.jetty:project:6.1-SNAPSHOT: checking for
updates from topicus-plugin-snapshot-repository
[INFO] No goals needed for project - skipping
[WARNING] Attempting to build MavenProject instance for Artifact
(org.apache.maven.plugins:maven-eclipse-plugin:2.7-20090529.071922-5)
of type: maven-plugin; constructing POM artifact instead.
[INFO] [eclipse:eclipse]
[INFO] Using Eclipse Workspace: /Workspaces/eduarte
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar:
/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
[INFO] Adding default classpath container:
org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] Resource directory's path matches an existing source directory.
Resources will be merged with the source directory src/main/java
[INFO] Resource directory's path matches an existing source directory.
Resources will be merged with the source directory src/test/java
[INFO] Not writing settings - defaults suffice
[INFO] Wrote Eclipse project for "myproject" to /Workspaces/eduarte/myproject.
[INFO]
   Javadoc for some artifacts is not available.
   Please run the same goal with the -DdownloadJavadocs=true
parameter in order to check remote repositories for javadoc.
   List of artifacts without a javadoc archive:
 o junit:junit:3.8.2
 o log4j:log4j:1.2.14
 o org.slf4j:slf4j-api:1.4.2
 o org.mortbay.jetty:jetty:6.1.4
 o org.mortbay.jetty:jetty-util:6.1.4
 o org.mortbay.jetty:servlet-api-2.5:6.1.4
 o org.mortbay.jetty:jetty-management:6.1.4
 o mx4j:mx4j:3.0.1
 o mx4j:mx4j-tools:3.0.1
 o org.slf4j:slf4j-log4j12:1.4.2

[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 18 seconds
[INFO] Finished at: Fri May 29 10:06:15 CEST 2009
[INFO] Final Memory: 9M/16M
[INFO] 


On Fri, May 29, 2009 at 9:20 AM, Arnaud HERITIER  wrote:
> I just deployed it in the snapshots repo. It's numbered
> : 2.7-20090529.071922-5Thx for your hard work Barrie.
> Cheers
>
>
> Arnaud
>
>
> On Fri, May 29, 2009 at 6:05 AM, Barrie Treloar  wrote:
>
>> On Wed, May 27, 2009 at 8:51 PM, Martijn Dashorst
>>  wrote:
>> > On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar 
>> wrote:
>> >> I went quickly hacking an existing IT test to include the resources
>> >> definition you provided and some debugging output (as ERROR so I could
>> >> see it)
>> >
>> > Great!
>> >
>> >> So src/main/resources is correctly on the resources list.
>> >> The problem is that the list of directories to parse is a Set and the
>> >> second addition is returning false to add() but nothing is checking
>> >> this condition.
>> >>
>> >> Now I need to work out how to handle the collision
>> >
>> > Let me know

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

On Wed, May 27, 2009 at 10:47 AM, Barrie Treloar  wrote:
> I went quickly hacking an existing IT test to include the resources
> definition you provided and some debugging output (as ERROR so I could
> see it)

Great!

> So src/main/resources is correctly on the resources list.
> The problem is that the list of directories to parse is a Set and the
> second addition is returning false to add() but nothing is checking
> this condition.
>
> Now I need to work out how to handle the collision

Let me know when there's a new snapshot to try.

Martijn


-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

http://wicket.apache.org/quickstart.html

Select for example Wicket 1.3.6

Martijn

On Wed, May 27, 2009 at 8:44 AM, Barrie Treloar  wrote:
> On Wed, May 27, 2009 at 3:58 PM, Martijn Dashorst
>  wrote:
>> With Wicket, we have Page.html, Page.properties, Page.properties_ru,
>> Page.js, Page.css, Page.younameit next to the Java files. This has
>> been the official way to work with Wicket, and was 100% supported by
>> maven by defining src/main/java as a resources element in our poms.
>> 443 breaks this. And no, we don't take put them in src/main/resources
>> as an answer.
>
> Can you attach to http://jira.codehaus.org/browse/MECLIPSE-551 a test
> project that is configured the way you expect.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

On Wed, May 27, 2009 at 1:17 AM, Barrie Treloar  wrote:
> On Tue, May 26, 2009 at 11:03 PM, Martijn Dashorst
>  wrote:
>> In my opinion  MECLIPSE-443 is a very bad idea. Should every plugin be
>> configured so that the resources available in src/main/java are
>> treated as classpath entries?
>
> It was my understanding that if you had resources in src/main/java
> that Maven would not package these.
> They must be in src/main/resources.

Unless you define src/main/java inside a  element as I
already mentioned. This should be the canonical place for defining
such project descriptions, *NOT* in every frakking plugin that doesn't
want to read the pom.

> What is wrong with configuring your ide to behave how Maven behaves?
> This will stop you having moments where it works in Eclipse but Maven fails.

Because the plugin doesn't configure my IDE as maven behaves: see above...

>> According to me the eclipse plugin
>> should take the  part of the pom into account, rather than
>> invent yet another way of specifying where resources live.
>
> The plugin takes it diirectly from the in memory copy of the pom via
> project.getBuild().getResources() as can be seen in the code below.
> It does not invent another way of specifying where resources live.

Then why doesn't it work? I don't care about how it is implemented in
Java code. Just either roll back 443, or implement it correctly.

>> This "fix" break so many existing builds and archetypes it is not fun
>> anymore. I for one don't like being the helpdesk for maven on the
>> Wicket user list.
>
> Can you be specific about what breaks?
> Which files, why they are in src/main/java and not somewhere else, etc.

With Wicket, we have Page.html, Page.properties, Page.properties_ru,
Page.js, Page.css, Page.younameit next to the Java files. This has
been the official way to work with Wicket, and was 100% supported by
maven by defining src/main/java as a resources element in our poms.
443 breaks this. And no, we don't take put them in src/main/resources
as an answer.

> For other edge cases 2.7 added
> http://jira.codehaus.org/browse/MECLIPSE-104, which allows you to
> configure what files can be included/excluded from source directories.

I'd qualify thousands of Wicket users as hardly an edge case thank you
very much/

> Without specifics it is impossible to fix your complaint.

I've complained about this earlier in the maven-eclipse-plugin-2.6
thread, together with specifics.

I don't want to have to configure my resources with every plugin that
is going to be part of the build. That is not the Maven way. If the
compiler plugin can copy all my resources by reading the 
part of my pom, why should the maven-eclipse-plugin behave any
different?

Martijn

-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

Yes, and I've been burned by m2eclipse, and haven't heard loving
reports from co-workers about q4e either. Not installing any of them
anytime soon.

Martijn

On Tue, May 26, 2009 at 4:09 PM, Arnaud HERITIER  wrote:
> Did you try to use m2eclipse or q4e ?They'll be the future.
>
> maven-eclipse-plugin will probably die under its own weight. There are too
> many use cases and testing coverage isn't conclusive because we only checks
> what we generate and not that we are able to import/use it in eclipse . We
> have really few developpers involved in it and the darkness of the eclipse
> configuration doesn't help. Now many settings are stored in files.
>
> I'll try to have a look at MECLIPSE-443 but I cannot say when it will be. I
> think it sould be better for you to be able to use plugins like m2eclipse or
> q4e.
>
> Arnaud
>
> On Tue, May 26, 2009 at 3:33 PM, Martijn Dashorst <
> martijn.dasho...@gmail.com> wrote:
>
>> In my opinion  MECLIPSE-443 is a very bad idea. Should every plugin be
>> configured so that the resources available in src/main/java are
>> treated as classpath entries? According to me the eclipse plugin
>> should take the  part of the pom into account, rather than
>> invent yet another way of specifying where resources live.
>>
>> This "fix" break so many existing builds and archetypes it is not fun
>> anymore. I for one don't like being the helpdesk for maven on the
>> Wicket user list.
>>
>> Martijn
>>
>> On Tue, May 26, 2009 at 9:21 AM, Arnaud HERITIER 
>> wrote:
>> > Hi Ari,
>> > Thanks for your feedback.
>> >
>> > Did you follow this doc to setup your eclipse project :
>> >
>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
>> > ??
>> >
>> > Arnaud
>> >
>> >
>> > On Tue, May 26, 2009 at 2:29 AM, ari.meyer  wrote:
>> >
>> >>
>> >> Hi Arnaud,
>> >>
>> >> I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and
>> I'm
>> >> getting the same error when using Wicket:
>> >>
>> >> org.apache.wicket.markup.MarkupNotFoundException: Markup not found.
>> >>
>> >> Reverting again back to 2.5.1, everything worked properly.
>> >>
>> >> Best regards,
>> >> Ari
>> >>
>> >>
>> >> Arnaud HERITIER wrote:
>> >> >
>> >> > Hi Community,
>> >> >   The recent release 2.6 of the maven-eclipse-plugin created many
>> >> problems
>> >> > for all of those who had/wanted to store non-java files under
>> src/*/java
>> >> > (which is required for wicket, ajdt, and probably others usecases).
>> >> >   Even we have many integration tests in this plugin we didn't notice
>> >> this
>> >> > issue because our testcases allow us to check that generated
>> >> configuration
>> >> > files aren't evolving and that we are able to import and use a project
>> in
>> >> > eclipse (too heavy to do).
>> >> >
>> >> >   To fix this issue we (Barrie to be honest) improved the plugin to
>> allow
>> >> > the usage of includes and excludes. :
>> >> > http://jira.codehaus.org/browse/MECLIPSE-104
>> >> >   The documentation of these feature is here :
>> >> >
>> >>
>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
>> >> > There are many broken links on the site and I don't know why. I'll
>> >> > investigate later.
>> >> > Others pages are the same in
>> >> > http://maven.apache.org/plugins/maven-eclipse-plugin/
>> >> > For AJDT project you can have a look at this page :
>> >> > http://maven.apache.org/plugins/maven-eclipse-plugin-
>> >> > 2.7-SNAPSHOT/examples/ajdt-projects.html
>> >> >
>> >> > To test the plugin you have to add in your project or in your settings
>> >> > this
>> >> > repository :
>> >> > https://repository.apache.org/content/repositories/snapshots/
>> >> > (be careful to the https protocol)
>> >> > The last version I deployed is : 2.7-20090416.000603-3
>> >> >
>> >> > Please, test it and give us your feedback. If it is posi

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

In my opinion  MECLIPSE-443 is a very bad idea. Should every plugin be
configured so that the resources available in src/main/java are
treated as classpath entries? According to me the eclipse plugin
should take the  part of the pom into account, rather than
invent yet another way of specifying where resources live.

This "fix" break so many existing builds and archetypes it is not fun
anymore. I for one don't like being the helpdesk for maven on the
Wicket user list.

Martijn

On Tue, May 26, 2009 at 9:21 AM, Arnaud HERITIER  wrote:
> Hi Ari,
> Thanks for your feedback.
>
> Did you follow this doc to setup your eclipse project :
> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
> ??
>
> Arnaud
>
>
> On Tue, May 26, 2009 at 2:29 AM, ari.meyer  wrote:
>
>>
>> Hi Arnaud,
>>
>> I just tested with maven-eclipse-plugin-2.7-20090427.230850-4.jar and I'm
>> getting the same error when using Wicket:
>>
>> org.apache.wicket.markup.MarkupNotFoundException: Markup not found.
>>
>> Reverting again back to 2.5.1, everything worked properly.
>>
>> Best regards,
>> Ari
>>
>>
>> Arnaud HERITIER wrote:
>> >
>> > Hi Community,
>> >   The recent release 2.6 of the maven-eclipse-plugin created many
>> problems
>> > for all of those who had/wanted to store non-java files under src/*/java
>> > (which is required for wicket, ajdt, and probably others usecases).
>> >   Even we have many integration tests in this plugin we didn't notice
>> this
>> > issue because our testcases allow us to check that generated
>> configuration
>> > files aren't evolving and that we are able to import and use a project in
>> > eclipse (too heavy to do).
>> >
>> >   To fix this issue we (Barrie to be honest) improved the plugin to allow
>> > the usage of includes and excludes. :
>> > http://jira.codehaus.org/browse/MECLIPSE-104
>> >   The documentation of these feature is here :
>> >
>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
>> > There are many broken links on the site and I don't know why. I'll
>> > investigate later.
>> > Others pages are the same in
>> > http://maven.apache.org/plugins/maven-eclipse-plugin/
>> > For AJDT project you can have a look at this page :
>> > http://maven.apache.org/plugins/maven-eclipse-plugin-
>> > 2.7-SNAPSHOT/examples/ajdt-projects.html
>> >
>> > To test the plugin you have to add in your project or in your settings
>> > this
>> > repository :
>> > https://repository.apache.org/content/repositories/snapshots/
>> > (be careful to the https protocol)
>> > The last version I deployed is : 2.7-20090416.000603-3
>> >
>> > Please, test it and give us your feedback. If it is positive this week,
>> > we'll launch the release process the next one.
>> >
>> > cheers,
>> >
>> > --
>> > Arnaud
>> >
>> >
>>
>> --
>> View this message in context:
>> http://n2.nabble.com/-maven-eclipse-plugin--We-need-your-help-to-test-the-future-2.7-tp2646905p2972277.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
>>
>>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

org.codehaus.woodstox:stax2-api:3.0.1:jar is wrong in repo1.maven.org

[Martijn Dashorst]

The md5 sum of the org.codehaus.woodstox:stax2-api:3.0.1:jar is the
same as the one coming from repository.codehaus.org, but the repo1 jar
file doesn't generate the same MD5. The codehaus hosted jar *does*
generate the correct MD5 sum.

Martijn

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

The co-worker reported back that the plugin works as advertised
(latest snapshot)

Martijn

On Tue, Apr 21, 2009 at 10:27 AM, Martijn Dashorst
 wrote:
> A co-worker tested it, and found it not working. He'll comment later.
>
> Martijn
>
> On Tue, Apr 21, 2009 at 12:20 AM, Arnaud HERITIER  wrote:
>> Ping ??Nobody wants to test it ?
>> Without your help, will never be able to produce a plugin which replies to
>> your needs.
>> Cheers,
>>
>> Arnaud
>>
>> On Thu, Apr 16, 2009 at 10:42 AM, Arnaud HERITIER wrote:
>>
>>> Hi Community,
>>>   The recent release 2.6 of the maven-eclipse-plugin created many problems
>>> for all of those who had/wanted to store non-java files under src/*/java
>>> (which is required for wicket, ajdt, and probably others usecases).
>>>   Even we have many integration tests in this plugin we didn't notice this
>>> issue because our testcases allow us to check that generated configuration
>>> files aren't evolving and that we are able to import and use a project in
>>> eclipse (too heavy to do).
>>>
>>>   To fix this issue we (Barrie to be honest) improved the plugin to allow
>>> the usage of includes and excludes. :
>>> http://jira.codehaus.org/browse/MECLIPSE-104
>>>   The documentation of these feature is here :
>>>
>>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
>>> There are many broken links on the site and I don't know why. I'll
>>> investigate later.
>>> Others pages are the same in
>>> http://maven.apache.org/plugins/maven-eclipse-plugin/
>>> For AJDT project you can have a look at this page :
>>> http://maven.apache.org/plugins/maven-eclipse-plugin-
>>> 2.7-SNAPSHOT/examples/ajdt-projects.html
>>>
>>> To test the plugin you have to add in your project or in your settings this
>>> repository :
>>> https://repository.apache.org/content/repositories/snapshots/
>>> (be careful to the https protocol)
>>> The last version I deployed is : 2.7-20090416.000603-3
>>>
>>> Please, test it and give us your feedback. If it is positive this week,
>>> we'll launch the release process the next one.
>>>
>>> cheers,
>>>
>>> --
>>> Arnaud
>>>
>>
>>
>>
>> --
>> Arnaud
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.5 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: [maven-eclipse-plugin] We need your help to test the future 2.7

[Martijn Dashorst]

A co-worker tested it, and found it not working. He'll comment later.

Martijn

On Tue, Apr 21, 2009 at 12:20 AM, Arnaud HERITIER  wrote:
> Ping ??Nobody wants to test it ?
> Without your help, will never be able to produce a plugin which replies to
> your needs.
> Cheers,
>
> Arnaud
>
> On Thu, Apr 16, 2009 at 10:42 AM, Arnaud HERITIER wrote:
>
>> Hi Community,
>>   The recent release 2.6 of the maven-eclipse-plugin created many problems
>> for all of those who had/wanted to store non-java files under src/*/java
>> (which is required for wicket, ajdt, and probably others usecases).
>>   Even we have many integration tests in this plugin we didn't notice this
>> issue because our testcases allow us to check that generated configuration
>> files aren't evolving and that we are able to import and use a project in
>> eclipse (too heavy to do).
>>
>>   To fix this issue we (Barrie to be honest) improved the plugin to allow
>> the usage of includes and excludes. :
>> http://jira.codehaus.org/browse/MECLIPSE-104
>>   The documentation of these feature is here :
>>
>> http://maven.apache.org/plugins/maven-eclipse-plugin-2.7-SNAPSHOT/examples/specifying-source-path-inclusions-and-exclusions.html
>> There are many broken links on the site and I don't know why. I'll
>> investigate later.
>> Others pages are the same in
>> http://maven.apache.org/plugins/maven-eclipse-plugin/
>> For AJDT project you can have a look at this page :
>> http://maven.apache.org/plugins/maven-eclipse-plugin-
>> 2.7-SNAPSHOT/examples/ajdt-projects.html
>>
>> To test the plugin you have to add in your project or in your settings this
>> repository :
>> https://repository.apache.org/content/repositories/snapshots/
>> (be careful to the https protocol)
>> The last version I deployed is : 2.7-20090416.000603-3
>>
>> Please, test it and give us your feedback. If it is positive this week,
>> we'll launch the release process the next one.
>>
>> cheers,
>>
>> --
>> Arnaud
>>
>
>
>
> --
> Arnaud
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: eclipse:eclipse suddenly adding including="**/*.java" to .classpath

[Martijn Dashorst]

On Thu, Apr 9, 2009 at 7:58 AM, Arnaud HERITIER  wrote:
> 1) The Maven convention and good practice is to put ressources files like
> *.txt in src/main/resources.

But *FORCING* this 'convention' on the world is a whole other thing.
One of the benefits of using maven is that you can adjust it to your
liking. Such as resources that *belong* to your java classes in the
same physical source folder. If this is the way forward with maven, I
assure you all Wicket projects will be switching to a build system
that doesn't enforce such things upon us.

Martijn

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

Root pom doesn't specify maven-eclipse-plugin version

[Martijn Dashorst]

Using maven 2.0.10, I ran into the maven-eclipse-plugin 2.6 bug fix
that excludes anything not Java from being on the classpath. I didn't
upgrade my eclipse plugin, and thought that as of 2.0.8 the root pom
specifies stable plugins for each release. Apparently,
maven-eclipse-plugin is not amongst the listed, fixed plugins, since I
got version 2.6 today.

Is there a reason why the eclipse plugin is not part of the root pom
specification?

The effective pom for my project suggests that the following plugins
have a version specified in the root pom:

maven-antrun-plugin:1.3
maven-assembly-plugin:2.2-beta-2
maven-clean-plugin:2.2
maven-compiler-plugin:2.0.2
maven-dependency-plugin:2.0
maven-deploy-plugin:2.4
maven-ear-plugin:2.3.1
maven-ejb-plugin:2.1
maven-install-plugin:2.2
maven-jar-plugin:2.2
maven-javadoc-plugin:2.5
maven-plugin-plugin:2.4.3
maven-rar-plugin:2.2
maven-release-plugin:2.0-beta-8
maven-resources-plugin:2.3
maven-site-plugin:2.0-beta-7
maven-source-plugin:2.0.4
maven-surefire-plugin:2.4.3
maven-war-plugin:2.1-alpha-2

And I know that it is prudent to have a version specified for each
build to ensure reproducability (as evidenced by todays hunt after the
inadvertent upgrade to eclipse 2.6)

Martijn

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

Re: presentation material on maven?

[Martijn Dashorst]

Try slideshare.net, for example: http://www.slideshare.net/tag/maven

Martijn

On Mon, Mar 16, 2009 at 7:53 PM, Erik Putrycz  wrote:
>
> I'm thinking of doing a presentation of maven - IAM - archiva/nexus to a
> software quality local association and I was wondering if there is any
> existing open source presentation material available on these topics?
>
> Erik.
> --
> http://blog.erikputrycz.net
> --
> View this message in context: 
> http://www.nabble.com/presentation-material-on-maven--tp22541480p22541480.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
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

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

Re: repo.mergere.com unreachable ??

[Martijn Dashorst]

This is what my local repo dugg up:

dashorst$ find . -name "*.pom" -exec grep -H mergere {} \;
./org/apache/maven/maven-parent/1/maven-parent-1.pom:
[EMAIL PROTECTED]
./org/apache/maven/maven-parent/4/maven-parent-4.pom:
[EMAIL PROTECTED]
./org/apache/maven/maven-parent/5/maven-parent-5.pom:
[EMAIL PROTECTED]
./org/apache/maven/maven-parent/6/maven-parent-6.pom:
[EMAIL PROTECTED]
./org/apache/maven/maven-parent/7/maven-parent-7.pom:
[EMAIL PROTECTED]
./org/apache/maven/maven-plugin-surrogate-parent/5/maven-plugin-surrogate-parent-5.pom:
 [EMAIL PROTECTED]
./org/apache/maven/plugins/maven-plugin-parent/2.0.1/maven-plugin-parent-2.0.1.pom:
 [EMAIL PROTECTED]
./org/codehaus/xfire/xfire-parent/1.2.2/xfire-parent-1.2.2.pom:
http://repo.mergere.com/maven2
./org/mortbay/jetty/project/6.0.0rc1/project-6.0.0rc1.pom:
http://repo.mergere.com/maven2/
./org/mortbay/jetty/project/6.0.1/project-6.0.1.pom:
mergere-public-repository
./org/mortbay/jetty/project/6.0.1/project-6.0.1.pom:
http://repo.mergere.com/maven2


On Thu, Sep 11, 2008 at 12:40 AM, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
> It could also be a plugin afiak.
>
> Martijn
>
> On Thu, Sep 11, 2008 at 12:33 AM, Martijn Dashorst
> <[EMAIL PROTECTED]> wrote:
>> Probably some rogue project that has the repo in its repository list
>> in its pom file that is either included directly or transitively. I've
>> heard this mergere repository problem earlier.
>>
>> Martijn
>>
>> On Wed, Sep 10, 2008 at 8:43 PM, David C. Hicks <[EMAIL PROTECTED]> wrote:
>>> My first attempt at a fix was to download 2.0.9, in case there was something
>>> built-in.  That didn't resolve the problem.  I'm pretty puzzled by it, too.
>>>  Setting up the mirror in my personal settings.xml did the trick to bypass
>>> the bad url.
>>>
>>> Thanks!
>>>
>>> Wendy Smoak wrote:
>>>>
>>>> On Wed, Sep 10, 2008 at 11:20 AM, David C. Hicks <[EMAIL PROTECTED]>
>>>> wrote:
>>>>
>>>>>
>>>>> I've been trying to build an example project, but the repository
>>>>> "repo.mergere.com" is causing me headaches.  It is apparently not online,
>>>>> yet Maven continues to try to download things from it.  I have looked in
>>>>> the
>>>>> pom.xml, my ~/.m2/settings.xml and MAVEN_HOME/conf/settings.xml, but I do
>>>>> not see this repository listed anywhere.  Is there some way to turn this
>>>>> thing off?
>>>>>
>>>>
>>>> The url has changed to http://repo.exist.com/maven2/ .  (Or you can
>>>> just use the central repo.)
>>>>
>>>> You can use mirrors to override the url, but you'll either need to
>>>> know what repository id it's using, or use mirrorOf=* to override all
>>>> repos.  See http://maven.apache.org/guides/mini/guide-mirror-settings.html
>>>> .
>>>>
>>>> What version of Maven are you using?  It's odd that you don't see the
>>>> repo in the project pom or the settings-- it makes me think you're
>>>> using a customized version of Maven that has that repo url built in.
>>>> If so, switching to the latest Maven 2.0.9 download should fix that.
>>>>
>>>>
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.3.4 is released
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.4 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: repo.mergere.com unreachable ??

[Martijn Dashorst]

It could also be a plugin afiak.

Martijn

On Thu, Sep 11, 2008 at 12:33 AM, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
> Probably some rogue project that has the repo in its repository list
> in its pom file that is either included directly or transitively. I've
> heard this mergere repository problem earlier.
>
> Martijn
>
> On Wed, Sep 10, 2008 at 8:43 PM, David C. Hicks <[EMAIL PROTECTED]> wrote:
>> My first attempt at a fix was to download 2.0.9, in case there was something
>> built-in.  That didn't resolve the problem.  I'm pretty puzzled by it, too.
>>  Setting up the mirror in my personal settings.xml did the trick to bypass
>> the bad url.
>>
>> Thanks!
>>
>> Wendy Smoak wrote:
>>>
>>> On Wed, Sep 10, 2008 at 11:20 AM, David C. Hicks <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>>>
>>>> I've been trying to build an example project, but the repository
>>>> "repo.mergere.com" is causing me headaches.  It is apparently not online,
>>>> yet Maven continues to try to download things from it.  I have looked in
>>>> the
>>>> pom.xml, my ~/.m2/settings.xml and MAVEN_HOME/conf/settings.xml, but I do
>>>> not see this repository listed anywhere.  Is there some way to turn this
>>>> thing off?
>>>>
>>>
>>> The url has changed to http://repo.exist.com/maven2/ .  (Or you can
>>> just use the central repo.)
>>>
>>> You can use mirrors to override the url, but you'll either need to
>>> know what repository id it's using, or use mirrorOf=* to override all
>>> repos.  See http://maven.apache.org/guides/mini/guide-mirror-settings.html
>>> .
>>>
>>> What version of Maven are you using?  It's odd that you don't see the
>>> repo in the project pom or the settings-- it makes me think you're
>>> using a customized version of Maven that has that repo url built in.
>>> If so, switching to the latest Maven 2.0.9 download should fix that.
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.4 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: repo.mergere.com unreachable ??

[Martijn Dashorst]

Probably some rogue project that has the repo in its repository list
in its pom file that is either included directly or transitively. I've
heard this mergere repository problem earlier.

Martijn

On Wed, Sep 10, 2008 at 8:43 PM, David C. Hicks <[EMAIL PROTECTED]> wrote:
> My first attempt at a fix was to download 2.0.9, in case there was something
> built-in.  That didn't resolve the problem.  I'm pretty puzzled by it, too.
>  Setting up the mirror in my personal settings.xml did the trick to bypass
> the bad url.
>
> Thanks!
>
> Wendy Smoak wrote:
>>
>> On Wed, Sep 10, 2008 at 11:20 AM, David C. Hicks <[EMAIL PROTECTED]>
>> wrote:
>>
>>>
>>> I've been trying to build an example project, but the repository
>>> "repo.mergere.com" is causing me headaches.  It is apparently not online,
>>> yet Maven continues to try to download things from it.  I have looked in
>>> the
>>> pom.xml, my ~/.m2/settings.xml and MAVEN_HOME/conf/settings.xml, but I do
>>> not see this repository listed anywhere.  Is there some way to turn this
>>> thing off?
>>>
>>
>> The url has changed to http://repo.exist.com/maven2/ .  (Or you can
>> just use the central repo.)
>>
>> You can use mirrors to override the url, but you'll either need to
>> know what repository id it's using, or use mirrorOf=* to override all
>> repos.  See http://maven.apache.org/guides/mini/guide-mirror-settings.html
>> .
>>
>> What version of Maven are you using?  It's odd that you don't see the
>> repo in the project pom or the settings-- it makes me think you're
>> using a customized version of Maven that has that repo url built in.
>> If so, switching to the latest Maven 2.0.9 download should fix that.
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Dependency from repository?

[Martijn Dashorst]

Talk to the hibernate guys—projects are responsible themselves for
ensuring uploads to the central repo. This is not an issue for the
maven team.

Martijn

On Wed, Aug 27, 2008 at 10:14 AM, Alexander Vaysberg <[EMAIL PROTECTED]> wrote:
> Hi,
> i have a problem with maven dependency for hiberante. Hibernate site show,
> that the hibernate-core 3.3.0, hibernate-anatationen-3.4.0 released. But i
> can't it's downloaded from repo1. Why?
>
> Alexander Vaysberg
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Managing repositories.

[Martijn Dashorst]

On Tue, Aug 26, 2008 at 12:55 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
> This is certainly a situation for a repository manager such as
> Archiva, Nexus, or Artifactory (not sure if this one has group Id
> filtering like the others, but it may). For more information:
> http://maven.apache.org/repository-management.html

Artifactory has that ability.

Martijn

-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Building AppFuse with mvn

[Martijn Dashorst]

This is not a question for the maven list, please ask at the appfuse
forums/lists.

Martijn

On Tue, Aug 19, 2008 at 12:44 PM, sam wun <[EMAIL PROTECTED]> wrote:
> Thanks for the quick fix.
>
> It built successfully.
>
> Now from the README.txt file in the project directory, it said:
>
> D:\DEV\samples\AppFuse\phonecards>type README.txt
> AppFuse Basic JSF Archetype
>
> ---
>
> If you're reading this then you've created your new project using Maven and
> appfuse-basic-jsf.  You have only created the shell of an AppFuse Java EE
> application.  The project object model (pom) is defined in the file
> pom.xml.
> The application is ready to run as a web application. The pom.xml file is
> pre-defined with Hibernate as a persistence model and JSF as the web
> framework.
>
> To get started, please complete the following steps:
>
> 1. Download and install a MySQL 5.x database from
>http://dev.mysql.com/downloads/mysql/5.0.html#downloads.
>
> 2. Run "mvn jetty:run-war" and view the application at
> http://localhost:8080.
>
> 3. More information can be found at:
>
>http://appfuse.org/display/APF/QuickStart+Guide
>
>
>
> But I don't have mysql in this windows Vista desktop.
>
> I have insalled mysql 5 in a linux server. How can I make connection from
> this project to the mysql server in a remote server (linux system)?
>
>
>
> Thanks
>
>
>
>
>
>> - Original Message -
>> From: Martijn Dashorst
>> Sent: 19/08/08 08:37 pm
>> To: Maven Users List
>> Subject: Re: Building AppFuse with mvn
>>
>> add a minus character before your DartifactId=
>>
>> Martijn
>>
>> On Tue, Aug 19, 2008 at 12:30 PM, sam wun <[EMAIL PROTECTED]> wrote:
>> > Hi, I tried to build my first AppFuse project following the link I
>> shown
>> > below,
>> >
>> > http://appfuse.org/display/APF/AppFuse+QuickStart
>> >
>> >
>> >
>> > But I hit the first error:
>> >
>> >
>> >
>> > D:\DEV\samples>mkdir AppFuse
>> >
>> > D:\DEV\samples>cd AppFuse
>> >
>> > D:\DEV\samples\AppFuse>mvn archetype:create
>> > -DarchetypeGroupId=org.appfuse.arche
>> > types -DarchetypeArtifactId=appfuse-basic-jsf
>> > -DremoteRepositories=http://static
>> > .appfuse.org/releases -DarchetypeVersion=2.0.2 -DgroupId=com.ip6.app
>> > DartifactId
>> > =phonecards
>> > [INFO] Scanning for projects...
>> > [INFO] Searching repository for plugin with prefix: 'archetype'.
>> > [INFO]
>> >
>> 
>> > [ERROR] BUILD FAILURE
>> > [INFO]
>> >
>> 
>> > [INFO] Invalid task 'DartifactId=phonecards': you must specify a valid
>> > lifecycle
>> >  phase, or a goal in the format plugin:goal or
>> > pluginGroupId:pluginArtifactId:pl
>> > uginVersion:goal
>> > [INFO]
>> >
>> 
>> > [INFO] For more information, run Maven with the -e switch
>> > [INFO]
>> >
>> 
>> > [INFO] Total time: < 1 second
>> > [INFO] Finished at: Tue Aug 19 20:24:11 EST 2008
>> > [INFO] Final Memory: 2M/4M
>> > [INFO]
>> >
>> 
>> >
>> > D:\DEV\samples\AppFuse>
>> >
>> >
>> > There is no reference related to the groupid and project name.
>> >
>> > What is the proper way to create this project?
>> >
>> >
>> >
>> > Thanks
>> >
>> >
>> >
>> >
>> >
>> >> - Original Message -
>> >> From: sam wun
>> >> Sent: 19/08/08 04:08 pm
>> >> To: Maven Users List, Maven Users List
>> >> Subject: Re: Re: simple online order form
>> >>
>> >> Hi,
>> >>
>> >>
>> >>
>> >> I am wondering is this AppFuse a widely use framework or library for
>> >> building form like this?
>> >>
>> >>
>> >>
>> >> Thanks
>> >>
>> >>
>> >>
>> >>

Re: Building AppFuse with mvn

[Martijn Dashorst]

add a minus character before your DartifactId=

Martijn

On Tue, Aug 19, 2008 at 12:30 PM, sam wun <[EMAIL PROTECTED]> wrote:
> Hi, I tried to build my first AppFuse project following the link I shown
> below,
>
> http://appfuse.org/display/APF/AppFuse+QuickStart
>
>
>
> But I hit the first error:
>
>
>
> D:\DEV\samples>mkdir AppFuse
>
> D:\DEV\samples>cd AppFuse
>
> D:\DEV\samples\AppFuse>mvn archetype:create
> -DarchetypeGroupId=org.appfuse.arche
> types -DarchetypeArtifactId=appfuse-basic-jsf
> -DremoteRepositories=http://static
> .appfuse.org/releases -DarchetypeVersion=2.0.2 -DgroupId=com.ip6.app
> DartifactId
> =phonecards
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'archetype'.
> [INFO]
> 
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Invalid task 'DartifactId=phonecards': you must specify a valid
> lifecycle
>  phase, or a goal in the format plugin:goal or
> pluginGroupId:pluginArtifactId:pl
> uginVersion:goal
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: < 1 second
> [INFO] Finished at: Tue Aug 19 20:24:11 EST 2008
> [INFO] Final Memory: 2M/4M
> [INFO]
> 
>
> D:\DEV\samples\AppFuse>
>
>
> There is no reference related to the groupid and project name.
>
> What is the proper way to create this project?
>
>
>
> Thanks
>
>
>
>
>
>> - Original Message -
>> From: sam wun
>> Sent: 19/08/08 04:08 pm
>> To: Maven Users List, Maven Users List
>> Subject: Re: Re: simple online order form
>>
>> Hi,
>>
>>
>>
>> I am wondering is this AppFuse a widely use framework or library for
>> building form like this?
>>
>>
>>
>> Thanks
>>
>>
>>
>>
>>
>> > - Original Message -
>> > From: Rusty Wright
>> > Sent: 19/08/08 04:37 am
>> > To: Maven Users List
>> > Subject: Re: simple online order form
>> >
>> > You could try looking at AppFuse:
>> >
>> > http://www.ibm.com/developerworks/java/library/j-appfuse/
>> >
>> >
>> > sam wun wrote:
>> > > Hi,
>> > >
>> > >
>> > >
>> > > I want to build a simple  online order with Struts, eclipse, and
>> tomcat
>> > > (mysql database).
>> > >
>> > > Is there any example/tutorial I can follow to create this simple
>> > project?
>> > >
>> > > I found many tutorials are based on MyEclipse, but I am using Elcipse
>> > 3.4.
>> > >
>> > >
>> > >
>> > > Thank  you in advance.
>> > >
>> > >
>> > >
>> > >
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: generating javadoc on one of the dependency jar

[Martijn Dashorst]

You can only generate JavaDoc from source, not from a binary jar. For
instance, parameter names are stripped in the binary code.

Martijn

On Wed, Aug 13, 2008 at 5:03 PM, Zemian Deng <[EMAIL PROTECTED]> wrote:
> Hello list,
>
> I have a commercial jar artifact that uploaded to my own repository, and I
> can access it fine. I want to gerenate a javadoc for this particular jar
> along with my project javadoc. Is this possible? Can someone show me what I
> have to do in pom to configure this?
>
> Thanks,
> -Zemian
>
> --
> Sweet - a Scala web framework:
> http://code.google.com/p/sweetscala
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: DistributionManagement using repository id

[Martijn Dashorst]

You could use a company repository manager, and reference that in a
parent pom that all your projects extend.

Martijn

On Fri, Aug 8, 2008 at 12:37 PM, Richard Chamberlain
<[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>
> In all of my POM files I have a distribution management section. Each
> one of them has the same URL to my companies internal repo.
>
>
>
> Is there a way to reference a repository in my settings.xml that I want
> to deploy the artefact to, rather than repeating in each pom file?
>
>
>
> I guess I could create a POM file that all my projects reference, but I
> think it would be neater in settings.
>
>
>
> I've tried:
>
>  
>
>
>
>  myrepo
>
>
>
>
>
>  false
>
>  myrepo
>
>
>
>
>
> But it doesn't seem to work.
>
>
>
> Thanks,
>
>
>
> Richard
>
>
>
> Richard Chamberlain
> Software Engineer | Caplin Systems Ltd
>
> Office: +44 (0)20 7826 9639
> Mobile: +44 (0)7720 686 064
> www.caplin.com 
>
>
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Does maven1 works with Java5?

[Martijn Dashorst]

http://maven.apache.org/maven-1.x/plugins/java/properties.html

On Mon, Jul 21, 2008 at 11:46 AM, thomas2004 <[EMAIL PROTECTED]> wrote:
>
> How and where can I set the compiler version?
>
>
>
> Martijn Dashorst wrote:
>>
>> make sure you set the compiler version correctly. The compiler plugin
>> defaults to java 1.3
>>
>> Martijn
>>
>> On Mon, Jul 21, 2008 at 11:35 AM, thomas2004 <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> I have a java project built with Java5. Today as I rebuild the project
>>> with
>>> maven1 I got error. It doesn't recognize the generics. I doubt the maven1
>>> doesn't work with Java5. Is it right?
>>>
>>> Regards
>>>
>>> Thomas
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Does-maven1-works-with-Java5--tp18565148p18565148.html
>>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.3.4 is released
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
> --
> View this message in context: 
> http://www.nabble.com/Does-maven1-works-with-Java5--tp18565148p18565311.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Does maven1 works with Java5?

[Martijn Dashorst]

make sure you set the compiler version correctly. The compiler plugin
defaults to java 1.3

Martijn

On Mon, Jul 21, 2008 at 11:35 AM, thomas2004 <[EMAIL PROTECTED]> wrote:
>
> I have a java project built with Java5. Today as I rebuild the project with
> maven1 I got error. It doesn't recognize the generics. I doubt the maven1
> doesn't work with Java5. Is it right?
>
> Regards
>
> Thomas
>
> --
> View this message in context: 
> http://www.nabble.com/Does-maven1-works-with-Java5--tp18565148p18565148.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: deployment of dependencies to company repository

[Martijn Dashorst]

Use a repository manager such as artifactory or archiva instead, and
let it download those dependencies for you. Or you can upload an
existing (local) repository to artifactory to seed the cache.

Martijn

On Wed, Jul 16, 2008 at 6:19 PM, Fisher, Jonathan
<[EMAIL PROTECTED]> wrote:
> Hey guys,
>
> I've searched the mailing list, and I don't believe this has been asked.
> We have a company wide maven repository.  We deploy our internal
> projects to this server, and we cache their dependencies (hibernate,
> spring, etc) there to speed up the build process (and reduce the
> bandwidth bill from accessing maven central all the time).
>
> Is there an efficient way to deploy all the dependencies in a project's
> pom to the company repository? I don't have the desire to do this
> anymore:
>
> mvn deploy:deploy -file hibernatejarforexample.jar
> -DgroupId=forexample.org.hibernate
> -DartifactId=hibernate
> -Dversion=3.2.6.ga
> -Dfile=path-to-hibernate-for-example-pom.xml
> -Dpackaging=pom
> -DrepositoryId=MycompanysInternalRepoId
> -Durl=http://internalrepo
>
> ...for each individual version of our 20 dependencies (junit, spring-*,
> hibernate, ect). Any help or suggestions to improve our process would be
> appreciated.
>
> Thank you,
>
> Jonathan Fisher
> Software Developer
> Argus Health Systems
> Ext. 39530 Bus. 816-843-9530
>
>
> PRIVILEGED AND CONFIDENTIAL
> This email transmission contains privileged and confidential information 
> intended only for the use of the individual or entity named above.  If the 
> reader of the email is not the intended recipient or the employee or agent 
> responsible for delivering it to the intended recipient, you are hereby 
> notified that any use, dissemination or copying of this email transmission is 
> strictly prohibited by the sender.  If you have received this transmission in 
> error, please delete the email and immediately notify the sender via the 
> email return address or mailto:[EMAIL PROTECTED]  Thank you.
>
>
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Canoo WebTest Plugin 0.2 for M2 is available for field testing ...

[Martijn Dashorst]

I've downloaded the latest (0.6.1) and built it from the source but
any plugin invocation results in npe's in maven. For example:

$ mvn help:describe -Dplugin=webtest -Dfull=true
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'help'.
WAGON_VERSION: 1.0-beta-2
[INFO] 
[INFO] Building quickstart
[INFO]task-segment: [help:describe] (aggregator-style)
[INFO] 
[INFO] [help:describe]
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] null
[INFO] 
[INFO] Trace
java.lang.NullPointerException
at 
org.apache.maven.plugins.help.DescribeMojo.describePlugin(DescribeMojo.java:452)
at 
org.apache.maven.plugins.help.DescribeMojo.execute(DescribeMojo.java:223)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] 
[INFO] Total time: 1 second
[INFO] Finished at: Wed Jul 02 17:42:11 CEST 2008
[INFO] Final Memory: 5M/508M
[INFO] 


On Thu, Oct 25, 2007 at 4:22 PM, Siegfried Goeschl
<[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> I created a rough cut of a M2 plugin to be downloaded from
>
> http://people.apache.org/~sgoeschl/download/maven-plugins/
>
> Krystian Novak did some field testing - thanks a lot  :-)
>
> A few points to keep in mind
>
> +) it is my very first M2 plugin so it could be quite shaky ...
> +) Canoo WebTest uses a lot of custom libraries - they are found in "lib"
> with a shell script to import them into the local repo
> +) the javax.mail-1.3.3.jar needs to be provided manually
> +) after some more testing it should go to Codehaus
>
> If someone feels brave enough - don't forget to provide feedback 
>
> Thanks in advance
>
> Siegfried Goeschl
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Publishing Source and Javadoc to Local Repository

[Martijn Dashorst]

See the maven source plugin, and attach it to the jar execution phase
(iirc.) you can see one example of the definition in action in the
Wicket parent pom:
http://svn.apache.org/repos/asf/wicket/trunk/pom.xml

Martijn

-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Package and Tag

[Martijn Dashorst]

I think you need the
mvn release:prepare release:perform

goals.

Martijn

On Nov 18, 2007 5:48 PM, Brad Smith <[EMAIL PROTECTED]> wrote:

> I use maven on several projects that provide components to other
> applications.  I would like to have maven automatically create a tag in
> the subversion repository for each time package is run to create a
> distributable jar from the project.  Is this possible?  If so, how might
> I accomplish this?
>
> Thanks,
>
> Brad
>
>


-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-rc1 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/

Re: Repostings (Was: RE: JDK6 compilation issue using Maven2 - annotations are not supported in -source 1.3)

[Martijn Dashorst]

gmail doesn't register your own messages as 'new'. as such your own
first posts hardly get noticed in gmail, only when someone responds
they light up.

This is at least what I've learned over the years.

Martijn

On 9/13/07, Tim Kettler <[EMAIL PROTECTED]> wrote:
> So when you reply to a message on this list or start a new thread with
> just a "To: Maven Users List " header, you don't
> recieve the sent mail via the mailinglist? This is working for me.
>
> -Tim
>
> Wayne Fay schrieb:
> > That explains a lot. And now that you mention it, something happened
> > to me the first time I posted... a while back.
> >
> > I wonder if we could perhaps ask (someone) about changing the
> > configuration of the mail list server, or something along those lines,
> > if this is what people are generally expecting.
> >
> > Wayne
> >
> > On 9/13/07, Anders Blehr <[EMAIL PROTECTED]> wrote:
> >> I can just answer for myself:
> >>
> >> I subscribed to the list yesterday and did my first 2 postings also
> >> yesterday.  We have similar lists internally at work and when I post to
> >> these I receive my own posts along with everyone else's posts.  However, it
> >> seems that here you do not receive your own posts.  So twice yesterday I 
> >> sat
> >> around wondering what happened to my posts and decided to resend slightly
> >> reworded versions of the original posts, thinking that some odd filter was
> >> at work.
> >>
> >> Cheers,
> >> - Anders.
> >>
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven-assembly-plugin to build simple jar

[Martijn Dashorst]

why don't you use a packaging of type 'jar'?

Martijn

On 4/1/07, raju <[EMAIL PROTECTED]> wrote:


Hi,

I just need to build a jar file containing the class files from a directory.
There are too many elements as part of the plugin.

Please provide me a pom snippet to achieve just jarring of files based on a
pattern-set.Currently i am using ant jar task for the same and calling that
with antrun-plugin.

Thanks in advance
Raju
--
View this message in context: 
http://www.nabble.com/Maven-assembly-plugin-to-build-simple-jar-tf3500378s177.html#a9775773
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Lifecycle and rebuilds

[Martijn Dashorst]

The consequences are pretty severe. This means I can't run a deploy
and an assembly phase at different times. Because the packaging is
required for the moduleSet type assembly, it will repackage my jar
files, and invalidate any signature created by the pgp plugin and
deployed to other locations.

Is there a way to prevent this from happening?

Martijn

On 3/21/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:

All,

I have a question that is bugging me for quite some time regarding
maven 2 and the build lifecycle.

Way back when I didn't use maven yet (2003) we used ant to automate
our build and everything was very efficient: compiles were only done
on java files that were actually changed, javadoc only generated when
a java file had been changed and tests only run ... you catch my
drift.

Now when I create a release using maven 2, I typically want to see if
things compile, test and create jar files from it. Typically one uses
mvn clean package for this feat.

Everything is nice, but when this is done, and you see that it works,
you want to install it into your local repository (nothing has
changed). So you type the magic: mvn install

I expect that this does not compile my classes (the compiler is
called, but rightfully doesn't generate class files again), but then
the unittests kick in. And javadoc, and the source plugin, and the jar
packaging again, before the install into the local repository happens.

If I then decide that it is time to deploy it to my remote repository,
then things get even nicer, because all the previous steps are
repeated again.

The question: why can't maven reuse already existing artifacts in the
target directory with a few simple file timestamps?

Martijn

--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org




--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Lifecycle and rebuilds

[Martijn Dashorst]

All,

I have a question that is bugging me for quite some time regarding
maven 2 and the build lifecycle.

Way back when I didn't use maven yet (2003) we used ant to automate
our build and everything was very efficient: compiles were only done
on java files that were actually changed, javadoc only generated when
a java file had been changed and tests only run ... you catch my
drift.

Now when I create a release using maven 2, I typically want to see if
things compile, test and create jar files from it. Typically one uses
mvn clean package for this feat.

Everything is nice, but when this is done, and you see that it works,
you want to install it into your local repository (nothing has
changed). So you type the magic: mvn install

I expect that this does not compile my classes (the compiler is
called, but rightfully doesn't generate class files again), but then
the unittests kick in. And javadoc, and the source plugin, and the jar
packaging again, before the install into the local repository happens.

If I then decide that it is time to deploy it to my remote repository,
then things get even nicer, because all the previous steps are
repeated again.

The question: why can't maven reuse already existing artifacts in the
target directory with a few simple file timestamps?

Martijn

--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Reduce memory-usage of maven 2

[Martijn Dashorst]

Probably the defaults for your jvm are too low. You can (read: should
be able to) increase the memory available for your Java runtime
environment by setting the following (assuming you use bash as a
shell):

export JAVA_OPTS=-Xmx512m

This should give you enough memory for maven to run in.

Martijn


On 9/10/06, Elias Gerber <[EMAIL PROTECTED]> wrote:

Hello everyone!

I am using Maven 2.0.4 for some of my (very small) projects. Now I
installed maven on a virtuall root server I own, and I would like to use
maven to do daily builds on that machine.

But if I run 'mvn package' there, I get the following exception:

java.io.IOException: java.io.IOException: Cannot allocate memory
at java.lang.UNIXProcess.(UNIXProcess.java:148)

(The full output is at the bottom of this E-Mail)

Now my question: Is it possible to reduce memory-usage of mvn? Or can I
not avoid it to buy (rent) some more RAM?

Thank you for any help.

Elias Gerber

output of mvn package:

[EMAIL PROTECTED]:~/modules/sudokusolver$ mvn package
[WARNING] Failed to initialize environment variable resolver. Skipping
environment substitution in settings.
---
constituent[0]:
file:/usr/local/maven-2.0.4/lib/maven-plugin-api-2.0.4.jar
constituent[1]:
file:/usr/local/maven-2.0.4/lib/wagon-file-1.0-alpha-7.jar
constituent[2]:
file:/usr/local/maven-2.0.4/lib/maven-artifact-manager-2.0.4.jar
constituent[3]:
file:/usr/local/maven-2.0.4/lib/maven-repository-metadata-2.0.4.jar
constituent[4]: file:/usr/local/maven-2.0.4/lib/maven-artifact-2.0.4.jar
constituent[5]: file:/usr/local/maven-2.0.4/lib/maven-core-2.0.4.jar
constituent[6]:
file:/usr/local/maven-2.0.4/lib/wagon-ssh-1.0-alpha-7.jar
constituent[7]: file:/usr/local/maven-2.0.4/lib/maven-profile-2.0.4.jar
constituent[8]: file:/usr/local/maven-2.0.4/lib/jsch-0.1.24.jar
constituent[9]: file:/usr/local/maven-2.0.4/lib/maven-settings-2.0.4.jar
constituent[10]:
file:/usr/local/maven-2.0.4/lib/doxia-sink-api-1.0-alpha-7.jar
constituent[11]: file:/usr/local/maven-2.0.4/lib/maven-model-2.0.4.jar
constituent[12]:
file:/usr/local/maven-2.0.4/lib/maven-plugin-descriptor-2.0.4.jar
constituent[13]: file:/usr/local/maven-2.0.4/lib/maven-project-2.0.4.jar
constituent[14]: file:/usr/local/maven-2.0.4/lib/maven-monitor-2.0.4.jar
constituent[15]:
file:/usr/local/maven-2.0.4/lib/wagon-http-lightweight-1.0-alpha-6.jar
constituent[16]:
file:/usr/local/maven-2.0.4/lib/maven-reporting-api-2.0.4.jar
constituent[17]: file:/usr/local/maven-2.0.4/lib/commons-cli-1.0.jar
constituent[18]:
file:/usr/local/maven-2.0.4/lib/wagon-provider-api-1.0-alpha-6.jar
constituent[19]:
file:/usr/local/maven-2.0.4/lib/wagon-ssh-external-1.0-alpha-6.jar
constituent[20]:
file:/usr/local/maven-2.0.4/lib/maven-plugin-parameter-documenter-2.0.4.jar
constituent[21]:
file:/usr/local/maven-2.0.4/lib/plexus-interactivity-api-1.0-alpha-4.jar
constituent[22]:
file:/usr/local/maven-2.0.4/lib/maven-plugin-registry-2.0.4.jar
constituent[23]:
file:/usr/local/maven-2.0.4/lib/maven-error-diagnostics-2.0.4.jar
---
java.io.IOException: java.io.IOException: Cannot allocate memory
at java.lang.UNIXProcess.(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at java.lang.Runtime.exec(Runtime.java:591)
at java.lang.Runtime.exec(Runtime.java:429)
at java.lang.Runtime.exec(Runtime.java:326)
at
org.codehaus.plexus.util.cli.CommandLineUtils.getSystemEnvVars(CommandLineUtils.java:177)
at
org.apache.maven.project.interpolation.RegexBasedModelInterpolator.(RegexBasedModelInterpolator.java:60)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at
org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:44)
at
org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93)
at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
at
org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:129)
at
org.codehaus.plexus.component.composition.Field

Re: Re: Re: Dependency scopes

[Martijn Dashorst]

Yes, but "runtime classpath" != "runtime scope"

runtime classpath == union(compile, runtime scope)

Martijn

On 8/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

So, this means that war and ear plug-ins reference the runtime classpath
instead of say compile or test. Correct?

"Martijn Dashorst" <[EMAIL PROTECTED]> wrote on 30.08.2006
15:37:56:

> No, but maven is also used to create war, ear and other distribution
> packages. These packages need those actual runtime dependencies inside
> them.
>
> So for testing I need junit, but not at runtime -> test scope
> For testing I may not have a need for oracle-jdbc (using hsqldb for
> unittests), but at runtime I will (if deploying on an oracle database)
> -> runtime scope.
>
> For testing I need the interfaces for the servlet api, but those
> interfaces are available at runtiime in the tomcat server for my web
> application. So the servlet api JAR (javax.servlet-2.3.jar) is needed
> for compile *and* test, but doesn't need to go into the WAR archive ->
> provided scope.
>
> hth.
>
> Martijn


 DISCLAIMER 
This message is intended only for use by the person
to whom it is addressed. It may contain information
that is privileged and confidential. Its content does
not constitute a formal commitment by Lombard
Odier Darier Hentsch Group and any of its affiliates.
If you are not the intended recipient of this message,
kindly notify the sender immediately and destroy this
message. Thank You.
*





--
Download Wicket 1.2.2 now! New Ajax components: Tree, TreeTable and ModalWindow
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Dependency scopes

[Martijn Dashorst]

No, but maven is also used to create war, ear and other distribution
packages. These packages need those actual runtime dependencies inside
them.

So for testing I need junit, but not at runtime -> test scope
For testing I may not have a need for oracle-jdbc (using hsqldb for
unittests), but at runtime I will (if deploying on an oracle database)
-> runtime scope.

For testing I need the interfaces for the servlet api, but those
interfaces are available at runtiime in the tomcat server for my web
application. So the servlet api JAR (javax.servlet-2.3.jar) is needed
for compile *and* test, but doesn't need to go into the WAR archive ->
provided scope.

hth.

Martijn

On 8/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

> On 8/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > The difference between the runtime and test scopes is also not very
> > clear to me.

"Nick Veys" <[EMAIL PROTECTED]> wrote on 17.08.2006 06:16:40:

> This was already answered, but the test dependencies aren't needed for
> "normal" runtime, so they are left out.  It allows you to pull in a
> test harness, or mock libraries during your tests but leave that out
> for "real" execution or packaging.

While I understand that certain libs may be required at compile time
but not compile time, I don't see what "normal" runtime means in terms
of Maven. Maven is a build system, it does not execute your
applications, so how can it have a runtime classpath? There is no
such thing as runtime Maven or is there?


 DISCLAIMER 
This message is intended only for use by the person
to whom it is addressed. It may contain information
that is privileged and confidential. Its content does
not constitute a formal commitment by Lombard
Odier Darier Hentsch Group and any of its affiliates.
If you are not the intended recipient of this message,
kindly notify the sender immediately and destroy this
message. Thank You.
*





--
Download Wicket 1.2.2 now! New Ajax components: Tree, TreeTable and ModalWindow
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Repo sync with Ibiblio

[Martijn Dashorst]

OK, thanks, I created a JIRA issue for the sync.

Martijn

On 8/28/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:

you have to ask for it, not automated yet

On 8/27/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Our repository is in the sync scripts of maven (thanks Carlos!), and
> I'm wondering if I have to do anything specific to get the sync
> triggered or whether it is now fully automated?
>
> Martijn
>
> --
> Download Wicket 1.2.2 now! New Ajax components: Tree, TreeTable and 
ModalWindow
> -- http://wicketframework.org
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
 -- The Princess Bride

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Download Wicket 1.2.2 now! New Ajax components: Tree, TreeTable and ModalWindow
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Repo sync with Ibiblio

[Martijn Dashorst]

Hi,

Our repository is in the sync scripts of maven (thanks Carlos!), and
I'm wondering if I have to do anything specific to get the sync
triggered or whether it is now fully automated?

Martijn

--
Download Wicket 1.2.2 now! New Ajax components: Tree, TreeTable and ModalWindow
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Howto: Assembly, type and extension

[Martijn Dashorst]

IIUC The assembly plugin is used to build distributable artifacts,
such as zips containing your project, documentation, installation
scripts, run scripts etc. It is not intended to be put into a
repository.

Maven only allows one artifact (the result of building your module)
per project/module. This is either a jar, war, ejb-jar, or ear. A
project/module cannot produce both a jar and a war. That is why the
packaging element is in your pom.

Now the second part of your question: what /is/ your second artifact
used for? Why do you want to produce a second artifact type from your
project/module?

Martijn

On 7/11/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:

Hi folks,

even after reading available docs (mini-howto's and plugin docs) I still don't 
know awhat I am missing:

In a module I've created a second artifact with a different classifier 
usilizing the assembly plugin. The artifact's type seems to be the assembly's 
id and the file extension (zip) is also defined in the assembly.xml. Now, how 
can I refer this artifact in another module? Basically I wanna unpack the zip 
file and add it as resource to my module. But if I add this artifact as 
dependency with its type, the artifact cannot be found. Somehow I must still 
miss something in the picture what the assembly plugin produces and the 
differences between a classifier and type with extension. Can someone enlighten 
me?

- Jörg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Download Wicket 1.2 now! Write Ajax applications without touching JavaScript!
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Assembly and parent pom

[Martijn Dashorst]

Barrie,

Thanks for the answers.


> Example setup:
> 
> foo
> foo-parent
> 1.0-SNAPSHOT
> pom
> 
>
> 
> 
> foo
> foo-parent
> 1.0-SNAPSHOT
> 
> bar
> jar
> 
>
> The first problem is the parent pom. Is the snapshot version of the
> parent pom updated when I build the bar project?

Maven does not build parent poms or dependencies on a project.
You must either have access to a repository that the artifact can be
downloaded from or manually run the mvn install command on each
dependency so it is installed into your local repository.


What I meant to say is that snapshot dependencies are always checked
against the remote repository, but does this also work for the parent
reference?

i.e.
foofooSNAPSHOT

in the bar project will update the dependency foo.foo-SNAPSHOT.jar on
every build.

Does the parent pom also get updated everytime the bar project gets built?

Martijn

--
Download Wicket 1.2 now! Write Ajax applications without touching JavaScript!
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Assembly and parent pom

[Martijn Dashorst]

All,

If you have a project setup where all your projects have a common
parent project, and some are dependend on the others, how can you
accomodate the downloaders of your assemblies such that they still can
build your project using maven if/when they are offline?

Example setup:

foo
foo-parent
1.0-SNAPSHOT
pom




   foo
   foo-parent
   1.0-SNAPSHOT

bar
jar


The first problem is the parent pom. Is the snapshot version of the
parent pom updated when I build the bar project?

How should I construct my (source) assembly for bar, such that it can
be compiled using maven, even when the foo-parent pom is not available
on the central repo (usually the case for snapshot versions)? Add
(somehow) the foo-parent.pom to the assembly and provide README
instructions to perform an install first on the parent pom?

Martijn

--
Download Wicket 1.2 now! Write Ajax applications without touching JavaScript!
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: mvn install with sources?

[Martijn Dashorst]

Attach the sources plugin to the install phase of the build.


true
org.apache.maven.plugins
maven-source-plugin


attach-sources

jar






On 7/5/06, Aleksei Valikov <[EMAIL PROTECTED]> wrote:

Hi.

I'd like to get sources for my jar artifacts installed into the local repo. I
usually do mvn (clean) install, but this only builds and copies the binary jar
into the repo. What should I do to get sources along?

Bye.
/lexi

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Download Wicket 1.2 now! Write Ajax applications without touching JavaScript!
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Project structure and releasing

[Martijn Dashorst]

Though I read on a separate thread on this list
(http://www.nabble.com/Top-level-POM-behaviour-t1825699.html#a4980080)
that doing a module based build is not working for separated projects.
That is why I didn't put a modules section in the parent project.

Here's the quote from Alexandre:

 begin quote 
Modules are meant to be built from the top project so you can work on
all of them at the same time. Don't try to build them separatly
because it won't work. If it's not what you want and you prefer
compiling each project separately, you should stick to normal SNAPSHOT
dependencies.
 end quote 

In our case, each project may have a separated build: wicket-spring is
a self contained project with its own website etc.

Am I not grokking something here? Should I add a modules section to my
parent project?

Martijn

On 7/1/06, Andrew Williams <[EMAIL PROTECTED]> wrote:

I may be wrong, but if your parent is, as in the book, a pom packaged
artifact with a module list then doing a release at that level should
prompt (with sensible defaults) the release of all the modules.

Andy

On Fri, 2006-06-30 at 21:29 +0200, Martijn Dashorst wrote:
> All,
>
> I've updated the structure of my projects that depend on one another
> to the structure as proposed in the better builds with maven book.
>
> The one problem I have with this way of building is the link to the
> parent project:
>
> 
> wicket
> wicket-parent
> 1.2-SNAPSHOT
> 
>
> Now I have to update all projects to perform a release of say version
> 1.2.1. Or is there a better way?
>
> BTW. All projects use snapshot dependencies as adviced earlier on this
> mailinglist.
>
> Martijn
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Download Wicket 1.2 now! Write Ajax applications without touching JavaScript!
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Project structure and releasing

[Martijn Dashorst]

All,

I've updated the structure of my projects that depend on one another
to the structure as proposed in the better builds with maven book.

The one problem I have with this way of building is the link to the
parent project:


   wicket
   wicket-parent
   1.2-SNAPSHOT


Now I have to update all projects to perform a release of say version
1.2.1. Or is there a better way?

BTW. All projects use snapshot dependencies as adviced earlier on this
mailinglist.

Martijn

--
Download Wicket 1.2 now! Write Ajax applications without touching JavaScript!
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Re: Assembly plugin with war packaging type fails to work properly

[Martijn Dashorst]

I fixed this by forcing the assembly 2.0.1 version in the plugin
management section of my projects. The only thing that isn't solved by
that is that the assembly id is appended to the filename.

Martijn

On 6/30/06, Edwin Punzalan <[EMAIL PROTECTED]> wrote:


The only difference between assembly:assembly and assembly:attached is
the object that they are working on.  The goal assembly:assembly uses
${executedProject} while assembly:attached uses ${project}.

So if assembly:attached works for you, then I suggest you use it.


Martijn Dashorst wrote:
> All,
>
> We have an examples project which has an artifact type of 'war'. The
> dependencies for the war are correct and for instance servlet api has
> scope 'provided'.
>
> The provided jars don't show up in the WAR file, which is what I want.
>
> Now the catch: I want to create a combined src/binary ZIP distribution
> using the assembly plugin that includes *ALL* dependencies such that
> people can import the zip file as a complete eclipse, intellij Idea or
> netbeans project without having to install maven, and download all
> dependencies.
>
> However, what ever I specify in my assembly descriptor, only compile
> time dependencies end up in the final zip.
>
> Is there any way to get this fixed? Can I override the dependency
> resolver such that the assembly ignores everything the war type tells
> it about dependencies?
>
> mvn clean site package assembly:attached
>
> seems to work. But I think the following should result in the same
> packaging:
>
> mvn clean site assembly:assembly
>
> Any comments?
>
> Martijn
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Download Wicket 1.2 now! Write Ajax applications without touching JavaScript!
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Assembly plugin with war packaging type fails to work properly

[Martijn Dashorst]

All,

We have an examples project which has an artifact type of 'war'. The
dependencies for the war are correct and for instance servlet api has
scope 'provided'.

The provided jars don't show up in the WAR file, which is what I want.

Now the catch: I want to create a combined src/binary ZIP distribution
using the assembly plugin that includes *ALL* dependencies such that
people can import the zip file as a complete eclipse, intellij Idea or
netbeans project without having to install maven, and download all
dependencies.

However, what ever I specify in my assembly descriptor, only compile
time dependencies end up in the final zip.

Is there any way to get this fixed? Can I override the dependency
resolver such that the assembly ignores everything the war type tells
it about dependencies?

mvn clean site package assembly:attached

seems to work. But I think the following should result in the same packaging:

mvn clean site assembly:assembly

Any comments?

Martijn

--
Download Wicket 1.2 now! Write Ajax applications without touching JavaScript!
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Assembly

[Martijn Dashorst]

I noticed that also, and created a JIRA issue for it:
http://jira.codehaus.org/browse/MASSEMBLY-112

Martijn

On 6/2/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Has anyone else noticed how the main jar file you create is now included
as a "dependency" when using the  in an assembly
file?



Now the zip I create has 2 copies of my main jar in it?  One under the
output directory for files picked up as dependencies and one under the
main directory?



BTW this is only occurring with 2.0.4 too...I reverted back to 2.0.3 and
did an assembly and the main file wasn't included twice.



--Rudy






--
Download Wicket 1.2 now! Write Ajax applications without touching JavaScript!
-- http://wicketframework.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: What scope is like 'provided' and 'test' together?

[Martijn Dashorst]

Hmm,

Why not use the scope in the same way as the class attribute in html?

This would give:

test provided

this should tell maven that the dependency is needed for test, compile
and is provided in a later stage by some container.

Martijn

On 2/6/06, Lee Meador <[EMAIL PROTECTED]> wrote:
> David,
>
> I am doing something sort of like you described and that seems to work. The
> work-around is to set the scope one way in a project that is depended on and
> then exclude it in a project that is dependant.
>
> It's just not very satisfying when what you want is to include the jar for
> regular  compile and test compile and for test run but not for normal run.
> and the options don't include that combination.
>
> Thanks.
>
> On 2/4/06, David H. DeWolf <[EMAIL PROTECTED]> wrote:
> >
> > Lee,
> >
> > Have you tried using the exclusions that are available within the
> > dependency declarations?
> >
> > If this webservices.jar is needed in a project (say project-a) which
> > is included within an ear (say ear-project), you would define the
> > following dependency within the ear-project pom:
> >
> > 
> >   whatever
> >   project-a
> >   1.0
> >   compile
> >   
> > 
> >   whatever
> >   webservices
> > 
> >   
> > 
> >
> > With this approach, you could use a compile scoped dependency but not
> > have it included in the ear.
> >
> > Hope that helps,
> >
> > David
> >
> > On 2/3/06, Lee Meador <[EMAIL PROTECTED]> wrote:
> > > I have a jar (webservices.jar) that I need for these things:
> > >
> > > 1) Compile main source.
> > > 2) Run tests in projects that are dependant on this one.
> > >
> > > But not for running the main source since that will run in the ejb
> > > container.
> > >
> > > provided doesn't work because the jar isn't available for
> > the
> > > tests in the dependent projects which need to instantiate a class from
> > the
> > > jar but not to call it.
> > > compile doesn't work because the jar ends up inside the
> > ear
> > > test doesn't work because the main code doesn't compile.
> > >
> > > Am I looking at this wrong somehow?
> > >
> > > The one solution I have found is to put it as "provided" in this project
> > and
> > > put it as 'test" in another project that runs tests that need classes.
> > (I
> > > use the term "project" to mean a think with a POM of its own.) The
> > problems
> > > with this are:
> > >
> > > 1) I can't run any such tests in the same project. (I can live with
> > this.)
> > > 2) I have to put the dependency in the other project even though it is
> > only
> > > needed when running the test that references this project. That seems
> > > "wrong" in some way.
> > >
> > > Any ideas?
> > >
> > > -- Lee Meador
> > > Sent from gmail. My real email address is [EMAIL PROTECTED]
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> -- Lee Meador
> Sent from gmail. My real email address is [EMAIL PROTECTED]
>
>


--
Living a wicket life...

Martijn Dashorst - http://www.jroller.com/page/dashorst

Wicket 1.1.1 is out: http://wicket.sourceforge.net/wicket-1.1

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Clover and licensed jar file

[Martijn Dashorst]

BTW this regards maven 2.

Martijn


On 12/19/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
>
> How can I use a licensed clover.jar instead of the 30-day trial jar file?
> Note I have a licensed clover.jar already :-)
>
> Martijn
>
>
> --
> Living a wicket life...
>
> Martijn Dashorst - http://www.jroller.com/page/dashorst
>
> Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1




--
Living a wicket life...

Martijn Dashorst - http://www.jroller.com/page/dashorst

Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1

Clover and licensed jar file

[Martijn Dashorst]

How can I use a licensed clover.jar instead of the 30-day trial jar file?
Note I have a licensed clover.jar already :-)

Martijn


--
Living a wicket life...

Martijn Dashorst - http://www.jroller.com/page/dashorst

Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1

Re: link broken on maven 2 site

[Martijn Dashorst]

http://maven.apache.org/plugins/maven-site-plugin/howto.html

at the bottom, a link points to the maven 1.0.2 site document, even though
it points to http://maven.apache.org/maven2/site.html

Martijn


On 12/18/05, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
>
> We already tried to do it.
> If you find some errors, don't hesitate to inform us on the mailing list
> or on jira.
>
> Cheers
>
> Arnaud
>
>
> > -Message d'origine-
> > De : Martijn Dashorst [mailto:[EMAIL PROTECTED]
> > Envoyé : dimanche 18 décembre 2005 22:32
> > À : Maven Users List
> > Objet : Re: link broken on maven 2 site
> >
> > THere are a lot of links broken, or pointing to non-relevant
> > Maven 1 documentation. Perhaps someone could do a clean
> > distribution of the maven 1 and 2 sites on the
> > maven.apache.org directory?
> >
> > Martijn
> >
> >
> > On 12/12/05, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi,
> > >
> > > on the http://maven.apache.org/guides/mini/guide-site.html
> > page, there
> > > is a link to the apt format documentation(
> > > http://maven.apache.org/guides/mini/apt-format.html),  but
> > this link
> > > seems broken.
> > >
> > > regards,
> > >
> > > Wim
> > >
> > >
> >
> >
> > --
> > Living a wicket life...
> >
> > Martijn Dashorst - http://www.jroller.com/page/dashorst
> >
> > Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1
> >
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Living a wicket life...

Martijn Dashorst - http://www.jroller.com/page/dashorst

Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1

Supplying your own maven-project-info-plugin reporters

[Martijn Dashorst]

All,

How should one change the way the project-info reports are generated?

For instance, I like to not show the email address of contributors and
developers, and fold some of the columns. How can I provide that
functionality?

Martijn


--
Living a wicket life...

Martijn Dashorst - http://www.jroller.com/page/dashorst

Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1

Re: link broken on maven 2 site

[Martijn Dashorst]

THere are a lot of links broken, or pointing to non-relevant Maven 1
documentation. Perhaps someone could do a clean distribution of the maven 1
and 2 sites on the maven.apache.org directory?

Martijn


On 12/12/05, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> on the http://maven.apache.org/guides/mini/guide-site.html page, there is
> a
> link to the apt format documentation(
> http://maven.apache.org/guides/mini/apt-format.html),  but this link seems
> broken.
>
> regards,
>
> Wim
>
>


--
Living a wicket life...

Martijn Dashorst - http://www.jroller.com/page/dashorst

Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1

Re: Is it possible to make pom.xml simpler?

[Martijn Dashorst]

e
> readeable.
> > > > > > I also think that mixing attributes with elements is in this
> case a
> > > bad idea and would hurt overall consistency.
> > > > > >
> > > > > > On 12/17/05, Srepfler Srgjan <[EMAIL PROTECTED]>
> wrote:
> > > > > > >
> > > > > > >
> > > > > > > >If your sole concern is the number of lines one must type, it
> is
> > > > > > > >certainly an option to have meta-pom.xml be in the format you
> > > > > > > >find most comfortable, then xslt it into the "more verbose"
> m2
> > > pom.xml.
> > > > > > > >
> > > > > > > >This argument of attributes versus elements has existed since
> the
> > > > > > > >dawn of [xml] time. I am not trying to argue one way or the
> > > > > > > >other, but since
> > > > > > > >m1 pom used the "more verbose" syntax, it eases the
> transition.
> > > > > > > >
> > > > > > > >  My USD$0.02,
> > > > > > > >  -- /v\atthew
> > > > > > > >
> > > > > > >
> >-
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > In fact people should develop a plugin that maps the
> simplified
> > > > > > > and verbose schemas on the fly :) The advantage of using
> > > > > > > namespaces is that you can create a your tag and map it to the
> > > > > > > verbose tag from the official pom.
> > > > > > > That's the way I've seen the spring guys use it for now but
> the
> > > > > > > advantage that I see is that in could be much easier to extend
> the
> > > > > > > pom and it would be more "type safe"
> > > > > > >
> > > > > > > My 0.02MKD
> > > > > > >
> > > > > > >
> --
> > > > > > > --- To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Alexandre Poitras
> > > > > Québec, Canada
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Regards,
> > > > _
> > > > Arik Kfir[EMAIL PROTECTED]
> > > >
> > > >
> > > >
> > > >
> -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > > --
> > > Regards,
> > > _
> > > Arik Kfir[EMAIL PROTECTED]
> > >
> >
> >
>
>
> --
> Regards,
> _
> Arik Kfir[EMAIL PROTECTED]
>



--
Living a wicket life...

Martijn Dashorst - http://www.jroller.com/page/dashorst

Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1

Re: Suggestion: Seperate list for M2?

[Martijn Dashorst]

-1 for me.

I find it very comforting to have one list on which I can ask all questions
maven. Be it working with 1.0.2, 1.1-beta2 or m2. I don't mind the high
traffic, and I also don't mind when people don't put m2 or m1 in the header
(it does help, though).

And I agree with RKS that the migration questions will fall into a gap.

Martijn

On 10/17/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> This is a stage when you'd get a number of
> "How do I do this m1.x function in m2?" questions
> from m1.x users. For this reason - and considering
> that we could prefix the subject with m1 or m2 -
> it seems like having separate lists right now is
> a bad idea, unless people largely Cc such topics
> to both the lists.
>
> Thanks,
>
> Rk
> x77309
>
> On Mon, 17 Oct 2005, Jeff Jensen wrote:
>
> > +1
> >
> > When I want both, I subscribe to both. When I want one, I subscribe to
> one.
> >
> >
> > Quoting Casper Thomsen <[EMAIL PROTECTED]>:
> >
> > > I doubt people will continue doing that for very long.
> > >
> > > In my opinion it makes no sense to have both in one list, since they
> are so
> > > different it would generate a large amount of noise for both groups of
> users.
> > >
> > > There is really not very much administrative overhead to creating an
> > > additional mailing list.
> > >
> > > /Casper
> > >
> > > -Original Message-
> > > From: Milos Kleint [mailto:[EMAIL PROTECTED]
> > > Sent: Mon 10/17/2005 15:46
> > > To: Maven Users List
> > > Subject: Re: Suggestion: Seperate list for M2?
> > >
> > > call me grumpy, but I don't want m3 or m4 to arrive. complete rewrites
> > > shouldn't be a daily routine.
> > >
> > > on the other hand a separate mailing list for m1 and m2 doesn't sound
> > > like a good idea. As long as people mention the version in the
> subject,
> > > it's fine with me.
> > >
> > >
> > > Milos
> > >
> > > Pilgrim, Peter wrote:
> > > > -1
> > > >
> > > > What happens when M3 or M4 arrive? Do you really keep creating a
> > > > maven list for each development release for now and forever?
> > > > Not to mention the headache it would cause admins how would
> > > > the mindgroup and knowledge for M1 users increase
> > > > when suddenly M2 whizbang innovation or discovery is discussed.
> > > >
> > > >
> > > > --
> > > > Peter Pilgrim :: J2EE Software Development
> > > > Operations/IT - Credit Suisse First Boston,
> > > > Floor 15, 5 Canada Square, London E14 4QJ, United Kingdom
> > > > Tel: +44-(0)207-883-4497
> > > >
> > > >
> > > >
> > > >> -Original Message-
> > > >> From: Xavier Toth [mailto:[EMAIL PROTECTED]
> > > >> Sent: 17 October 2005 13:40
> > > >> To: Maven Users List
> > > >> Subject: Re: Suggestion: Seperate list for M2?
> > > >>
> > > >>
> > > >> +1
> > > >>
> > > >> On 10/17/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote:
> > > >>
> > > >>> +1
> > > >>>
> > > >>> On 10/17/05, David Sag <[EMAIL PROTECTED]> wrote:
> > > >>>
> > >  I second that - a separate m2 list would be welcome
> > > 
> > >  Kind regards,
> > >  Dave Sag
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  "Siegfried Heintze" <[EMAIL PROTECTED]> wrote on
> > > 
> > > >> 17/10/2005 03:46:37
> > > >>
> > >  AM:
> > > 
> > > 
> > > > Just a suggestion: should there not be a separate list for M2?
> > > >
> > > > Siegfried
> > > >
> > > >
> > > >
> > > >
> > > >>
> -
> > > >>
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > > >>>
> > > >>>
> > > >
> > > >
> > >
> ==
> > > > Please access the attached hyperlink for an important electronic
> > > communications disclaimer:
> > > >
> > > > http://www.csfb.com/legal_terms/disclaimer_external_email.shtml
> > > >
> > > >
> > >
> ==
> > > >
> > > >
> > > >
> -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

[1.1b2] unable to build distribution

[Martijn Dashorst]

All,

I'm having troubles to build the wicket distribution using the maven
distribution plugin. I have modified the plugin to some degree, but I
doubt that is causing the problem.

This happens both in windows xp and mac osx. Both use jdk 1.4, and
maven 1.1-b2. The strangest thing is that when I run the maven site
plugin, everything goes well.

The error I get is the following (I skipped the javadoc generation etc):

~/Documents/workspace/wicket$ maven dist
<... snip ...>
[echo] Generating the Unit Tests...
junit-report:report:
java:prepare-filesystem:

java:compile:
[echo] Compiling to target/classes
[echo]
==

  NOTE: Targetting JVM 1.4, classes
  will not run on earlier JVMs

==


java:jar-resources:

test:prepare-filesystem:

test:test-resources:

test:compile:

test:test:
[junit] Running wicket.util.time.TimeTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.732 sec
<... many tests ...>
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.01 sec


BUILD FAILED
File.. /Users/martijn/.maven/cache/maven-xdoc-plugin-1.9.2/plugin.jelly
Element... x:parse
Line.. 122
Column -1
Error on line 28637 of document  : Parser has reached the entity
expansion limit "64,000" set by the Application. Nested exception:
Parser has reached the entity expansion limit "64,000" set by the
Application.
Total time   : 1 minutes 12 seconds
Finished at  : Wednesday, October 5, 2005 1:21:20 AM CEST

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Jar tampered while transiting from repository?

[Martijn Dashorst]

Check the MD5 sum?

Martijn

Hugues Pisapia wrote:


Hi there,

Is there a way we can be sure that jar files are not tampered while  
transiting from remote repositories to the local repository?
My guess would be to use https, but the repository would have to  
support this.


- Hugues

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

M2 transitive dependencies and releasing with M1

[Martijn Dashorst]

All,

I'm currently releasing Wicket and we have 2 projects: wicket and 
wicket-extensions. The extensions project has a dependency on wicket.


When I create a new version of wicket, do I need to release a new, 
updated version of extensions as well?


Or is this automatically resolved with m2?

Martijn

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Website layout, multiple releases and maven projects

[Martijn Dashorst]

BTW, I think I have answered my own question on what the best option is 
between the two scenarios I described (the multiple deployment strategy 
is my preferred one, as it doesn't break much).


But comments from others are much appreciated.

Martijn

Martijn Dashorst wrote:


All,

As the release and site manager of the Wicket project, I am trying to 
come up with a good scheme for uploading maven generated sites and 
putting this in projects.


Currently we have all documentation in the xdocs folder of the Wicket 
project. I can simple do a

maven clean site:deploy
in order to have the new content to be available on the website.

The problem arises when you have multiple versions of your project. We 
currently have 1.0 out there, and development is busy on 1.1


In order to support linking to online documentation, and not have 
those links become outdated, and in order to have an archive of the 
released versions documentation wise, I want to adopt the following 
layout:


htdocs/
htdocs/wicket-1.0
htdocs/wicket-1.1
htdocs/wicket-x.y

Method 1: Seperate projects

Build and javadoc information should go into the wicket-x.y 
subdirectories, and will be generated as a normal maven java project. 
Sub versions will overwrite the contents of each wicket-x.y subdirectory.


The main documentation (examples, feature lists, news, etc) are put 
into the root and or special subdirectories. This part of the site is 
generated from a seperate, special purpose project.


Method 2: One project, multi deployments
==
Another option is to keep the structure the way it currently is, and 
deploy the main site from the head of the trunc, and each release (and 
update) to the subdirectories.


What is wisdom in my case. Has anyone else got a great idea for this?

Martijn


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Website layout, multiple releases and maven projects

[Martijn Dashorst]

All,

As the release and site manager of the Wicket project, I am trying to 
come up with a good scheme for uploading maven generated sites and 
putting this in projects.


Currently we have all documentation in the xdocs folder of the Wicket 
project. I can simple do a

maven clean site:deploy
in order to have the new content to be available on the website.

The problem arises when you have multiple versions of your project. We 
currently have 1.0 out there, and development is busy on 1.1


In order to support linking to online documentation, and not have those 
links become outdated, and in order to have an archive of the released 
versions documentation wise, I want to adopt the following layout:


htdocs/
htdocs/wicket-1.0
htdocs/wicket-1.1
htdocs/wicket-x.y

Method 1: Seperate projects

Build and javadoc information should go into the wicket-x.y 
subdirectories, and will be generated as a normal maven java project. 
Sub versions will overwrite the contents of each wicket-x.y subdirectory.


The main documentation (examples, feature lists, news, etc) are put into 
the root and or special subdirectories. This part of the site is 
generated from a seperate, special purpose project.


Method 2: One project, multi deployments
==
Another option is to keep the structure the way it currently is, and 
deploy the main site from the head of the trunc, and each release (and 
update) to the subdirectories.


What is wisdom in my case. Has anyone else got a great idea for this?

Martijn


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to send build status in email...

[Martijn Dashorst]

Arik Kfir wrote:

The only problem I found with CC is lack of (sufficient) 
documentation. Once you're up and running, it's quite good though. I 
feel that newcomers to CC do have a hard time getting started with it.


I have had this problem also, but I have seen the documentation improve 
quite a bit since 2.1. 2.2 is very well documented I think. And the PDF 
I'm pointing to is also excellent: you don't need anything more to get 
started.


Martijn




Martijn Dashorst wrote:


Eric Pugh wrote:

A little off topic, but why wouldn't you use CruiseControl (or any 
of the other tools out there?)


CC has good Maven support, an okay reporting interface, and is 
scalable.   I'd hazard that you could get a basic build up and 
running in the required 15 minutes for a sniff test!  Well, after 
running Ant and compiling the app I guess..




In the new version this isn't necessary anymore (I believe). For a 
perfect getting started manual, take a look at the 
http://www.pragmaticautomation.com website and read the sample 
chapter(s) from the corresponding book. It's an excellent read!


Martijn

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to send build status in email...

[Martijn Dashorst]

Eric Pugh wrote:

A little off topic, but why wouldn't you use CruiseControl (or any of 
the other tools out there?)


CC has good Maven support, an okay reporting interface, and is 
scalable.   I'd hazard that you could get a basic build up and running 
in the required 15 minutes for a sniff test!  Well, after running Ant 
and compiling the app I guess..


In the new version this isn't necessary anymore (I believe). For a 
perfect getting started manual, take a look at the 
http://www.pragmaticautomation.com website and read the sample 
chapter(s) from the corresponding book. It's an excellent read!


Martijn

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: JUnit testing with Maven

[Martijn Dashorst]

A_Chitra wrote:

 
Hello all,

I have two projects (two enterprise applications) developed in RAD.  One 
application has JUnit test cases to test the other application.  Is it possible 
to  automate the testing using Maven.  Please advise me.
 

You'd have to do a multiproject in order for this to work. Are you 
talking about unit testing without the need of a deployed application, 
or integration testing on a deployed application?


The requirements for both in terms of server availability are disjunct, 
and consequently you'd need different plugins to do so.
I only have experience using the standard test plugin. But there are 
people who use maven for integration testing etc.



Martijn


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [checkstyle] Enabling HTML reports for checkstyle

[Martijn Dashorst]

Don't run the checkstyle plugin directly, but use the site plugin.
Martijn
Vinod Panicker wrote:
Hi,
Is there any way in which HTML reports can be made for the checkstyle plugin?
Currently its producing a .txt and a .xml file
Regards,
Vinod.
PS: Couldn't search the archives coz the site was giving a 502 - Bad
Gateway error.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven 2 error

[Martijn Dashorst]

comment out the jdbc dependency in the velocity.pom in the m2
repository. This will enable m2 to generate the project.

Martijn


Simon Matic Langford wrote:

>alas, I'm trying to create the pom file using m2, so I don't have any
>dependencies
>yet, I don't even have a pom file.
> 
>
>  
>
>>-Original Message-
>>From: BADIHI David [mailto:[EMAIL PROTECTED] 
>>Sent: 29 April 2005 17:17
>>To: Maven Users List
>>Subject: RE: Maven 2 error
>>
>>
>>Hi,
>>
>>You can put the missing jar in your repository, then in your 
>>POM file, indicate its name.
>>
>>Example :
>>
>>
>>
>>  struts
>>  struts
>>  1.1
>>
>>
>>
>>
>>-Message d'origine-
>>De : Simon Matic Langford [mailto:[EMAIL PROTECTED] 
>>Envoyé : vendredi 29 avril 2005 18:08
>>À : users@maven.apache.org
>>Objet : Maven 2 error
>>
>>Hi,
>>
>>I downloaded maven2 and tried to follow the getting started 
>>instructions, so I ran:
>>
>>m2 archetype:create -DgroupId=com.pcmsgroup.v21.common.logging
>>-DartifactId=v21-common-logging
>>
>>as detailed, and once I'd sorted my proxy settings, all 
>>looked well, until I got the little stack trace at the end. 
>>From what I could find on mailing lists it seems to be an 
>>invalid or missing dependency, how can I fix it? Also where'd 
>>the wiki go? FAQ's for M2 would be quite handy.
>>
>>Thanks
>>
>>Simon
>>
>>
>>org.apache.maven.reactor.ReactorException: Error executing 
>>project within the reactor
>>at 
>>org.apache.maven.DefaultMaven.execute(DefaultMaven.java:144)
>>at org.apache.maven.cli.MavenCli.main(MavenCli.java:233)
>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>at
>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
>>orImpl.jav
>>a:39)
>>at
>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
>>odAccessor
>>Impl.java:25)
>>at java.lang.reflect.Method.invoke(Method.java:324)
>>at
>>org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
>>at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
>>at
>>org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
>>at org.codehaus.classworlds.Launcher.main(Launcher.java:363)
>>Caused by: 
>>org.apache.maven.lifecycle.LifecycleExecutionException: Error 
>>during lifecycle execution
>>at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(De
>>faultLifec
>>ycleExecutor.java:154)
>>at
>>org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212)
>>at 
>>org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136)
>>... 9 more
>>Caused by:
>>org.apache.maven.artifact.resolver.ArtifactResolutionException
>>: Error transitively resolving artifacts:
>>at
>>org.apache.maven.artifact.resolver.DefaultArtifactResolver.res
>>olveTransi
>>tively(DefaultArtifactResolver.java:191)
>>at
>>org.codehaus.plexus.DefaultArtifactEnabledContainer.addCompone
>>nt(Default
>>ArtifactEnabledContainer.java:183)
>>at
>>org.apache.maven.plugin.DefaultPluginManager.addPlugin(Default
>>PluginMana
>>ger.java:299)
>>at
>>org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(Defa
>>ultPluginM
>>anager.java:272)
>>at
>>org.apache.maven.plugin.DefaultPluginManager.verifyPluginForGo
>>al(Default
>>PluginManager.java:219)
>>at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyMojo
>>Phase(Defa
>>ultLifecycleExecutor.java:377)
>>at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoa
>>lChain(Def
>>aultLifecycleExecutor.java:353)
>>at
>>org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(De
>>faultLifec
>>ycleExecutor.java:136)
>>... 11 more
>>Caused by:
>>org.apache.maven.artifact.resolver.TransitiveArtifactResolutio
>>nException
>>: Error retrieving metadata [jdbc:jdbc:jar:2.0] :
>>at
>>org.apache.maven.artifact.resolver.DefaultArtifactResolver.col
>>lect(Defau
>>ltArtifactResolver.java:307)
>>at
>>org.apache.maven.artifact.resolver.DefaultArtifactResolver.res
>>olveTransi
>>tively(DefaultArtifactResolver.java:187)
>>... 18 more
>>Caused by:
>>org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException:
>>Unable to read the metadata file
>>at
>>org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMe
>>tadataSour
>>ce.java:89)
>>at
>>org.apache.maven.artifact.resolver.DefaultArtifactResolver.col
>>lect(Defau
>>ltArtifactResolver.java:303)
>>... 19 more
>>Caused by: org.apache.maven.project.ProjectBuildingException: 
>>Unable to find artifact: jdbc:jdbc:pom:2.0
>>at
>>org.apache.maven.project.DefaultMavenProjectBuilder.findModelF
>>romReposit
>>ory(DefaultMavenProjectBuilder.java:167)
>>at
>>org.apache.maven.project.DefaultMavenProjectBuilder.buildFromR
>>epository(
>>DefaultMavenProjectBuilder.java:149)
>>at
>>org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMe
>>t

Plugin for generating netbeans project files from pom?

[Martijn Dashorst]

Hi,

Is there a netbeans plugin similar to the maven-eclipse-plugin,
maven-idea-plugin, or maven-FAVORITE_IDE-plugin?

I can't seem to find one.

Martijn

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Firebird DB/Jaybird JDBC Driver

[Martijn Dashorst]

Jamie Bisotti wrote:

>Our project is using Firebird DB and its Jaybird JDBC driver.  I can't
>seem to find Jaybird on Ibiblio; nor any mention of Maven/Jaybird in
>either projects mailing lists.  Is anyone using Maven with
>Firebird/Jaybird?  If so, how are you handling the dependency?
>  
>
I don't use firebird, or jaybird, but you have two options: request the
project to create an upload request for ibiblio, so the jar is hosted
there

Or... put the jar in your local repo yourself.

Martijn


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven site

[Martijn Dashorst]

Stephen Gray wrote:
Thanks very much for that. I have one question though. If you use the goals
in maven.xml to deploy the site will they ever be seen? Is cruisecontrol not
going to be in a continuous loop?
 

I don't understand what your concern is here. A goal in a maven.xml is 
almost the same as a plugin. In your cruisecontrol build spec, you can 
use the maven cruisecontrol plugin (the maven runner for cruisecontrol, 
not the plugin to generate cruisecontrol.xml files!) to run a build 
using maven, instead of the more common ant runner. This plugin allows 
you to give a goal to execute when CC is building your software. You can 
specify your maven.xml goal there as wel as a list of goals (instead of 
using the maven.xml file). So instead of creating a maven.xml file, you 
can also specify:
   jar:deploy-snapshot,site,site:sshdeploy

And if you are concerned this will create a loop in CC (which normally 
won't happen), you can always try it before you leave for the weekend, 
and monitor the output. No harm done then...

Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven site

[Martijn Dashorst]

Stephen Gray wrote:
Im actually using CruiseControl. How would that be implemented?
 

Add a goal 'site:sshdeploy' to your goal list in CruiseControl. Or you 
could create a maven.xml with a special cc goal which performs the build 
and site deploy as you would do manually.

maven.xml:
...

   
   
   

You have to make sure the sshdeploy (or fsdeploy) work automatically 
when you run them from within CC. This depends on under which user you 
run your CC build, etc.

Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven site

[Martijn Dashorst]

Stephen Gray wrote:
Hi,
How does the maven site refresh itself with the latest reports. Is it
necessary to deploy the site everytime to refresh it?
 

Yes. But you could use CruiseControl (or a similar product) to do that 
for you...

Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: New Maven Site is Live

[Martijn Dashorst]

James Mitchell wrote:
Fantastic!  Very nice job Brett!
Is there any way you can publish a zip of the site for offline 
browsing? I've needed that on many occasions.  If not, would you mind 
if I put one together and publish it? 
+1, especially the plugin documentation would be nice to have available 
for offline browsing.

Martijn Dashorst
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: New Maven Site is Live

[Martijn Dashorst]

Brett Porter wrote:
The new Maven web site has now gone live at http://maven.apache.org/.
After pointing everyone at the staging site for some time now, this
was a long overdue overhaul that hopefully makes documentation easier
to find, and more complete.
 

Thanks Brett,
I was anxious for the staging site to become public. This seems to cover 
the maven project much better than the old site structure. Congratulations!

You may add the following projects to the 'powered by' section:
- wicket (http://wicket.sf.net), a component oriented web framework
- jwebunit (http://jwebunit.sf.net), a testing framework for testing 
web applications

With regards,
Martijn Dashorst
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Excluding documents fom xdocs in site generation

[Martijn Dashorst]

Tedi Zanfolim wrote:
Hi,
 Is there anyway I could exclude some files from xdoc processing (without moving the files outside the directory) or asking xdoc to not validate the generated docs?
 I would like to generate my project site with all the documentation available in my 'documents' directory, so I pointed maven.docs.src to it. My problem is that I have some invalid xml documents in this directory (actually, entity fragments) and xdocs is trying to process them ...
 

AFAIK this is not possible using the POM. However you could copy the 
files before the XDOC plugin runs (as a preGoal) into a temp directory 
(under target) and point the maven.docs.src to that directory.

Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: artifacts and JDK version

[Martijn Dashorst]

But when is m2 due? Please don't say 'its done when its done'. Most 
developers can't wait until then.

I don't think this is too hard to add, just as adding the type of 
dependency (runtime, compiletime, testtime). If this could make it into 
maven 1.1 then many people would be happy.

Martijn
Arnaud HERITIER wrote:
I think that this feature will be available in m2.
But in m1 I don't think we'll support it.
Arnaud
On Mon, 28 Feb 2005 13:23:32 +0100, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
 

This sounds like a good option. I'm +1.
Martijn
Nicolas De Loof wrote:
   

Hi,
I've got some troubles using ibiblio as source for binaries because my
project runs on JDK1.3. Some artifacts on repository are compiled on
java 1.4 or 5.0 and don't run on JDK 1.3
For example, my project uses commons-dbcp and securityfilter. The
first required to be rebuilt (using it's ant script, not maven POM) to
"comment" JDBC 3.0 specific code, not usable on JDK 1.3. Second one is
build using JDK 5.0 and classloading failed.
Is they're some plan to add property to artifacts in repo that gives
minimal Java version ? I think it may be set in Manifest, but I've
never seen this info.
Nico.
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Junit with maven does it work

[Martijn Dashorst]

Krikor Krumlian wrote:
Hello everyone
 Has anyone been able to make junit tests work in maven ? If yes
can you show me the dependency you used maven version and
the  stuff .
It seems so easy and should work but for some reason i have not been
able to .
thank you

Try the 'maven genapp' plugin, which will provide you with a Java 
project which has all you need to answer your question(s).

Martijn
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: artifacts and JDK version

[Martijn Dashorst]

This sounds like a good option. I'm +1.
Martijn
Nicolas De Loof wrote:
Hi,
I've got some troubles using ibiblio as source for binaries because my 
project runs on JDK1.3. Some artifacts on repository are compiled on 
java 1.4 or 5.0 and don't run on JDK 1.3

For example, my project uses commons-dbcp and securityfilter. The 
first required to be rebuilt (using it's ant script, not maven POM) to 
"comment" JDBC 3.0 specific code, not usable on JDK 1.3. Second one is 
build using JDK 5.0 and classloading failed.

Is they're some plan to add property to artifacts in repo that gives 
minimal Java version ? I think it may be set in Manifest, but I've 
never seen this info.

Nico.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]