Re: Formerly Aether, now Maven Artifact Resolver--documentation?

Am 03/07/17 um 00:06 schrieb Laird Nelson: > Ah! After some more bashing around in Github and Maven central searching, > I found this: > https://github.com/apache/maven/blob/master/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/MavenRepositorySystemUtils.java > > This

Re: Where to keep test only files that are needed in multiple projects?

Am 12/23/16 um 16:50 schrieb Florian Schätz: > > > On 23/12/2016 09:48, Christian Schulte wrote: > >> I'd move those re-useable test classes into theire own module. For the >> example mentioned above, you would add commons-lang as a compile >> dependency to that

Re: Where to keep test only files that are needed in multiple projects?

Am 12/23/16 um 09:39 schrieb Dirk Olmes: > On 12/22/2016 03:43 PM, João Cabrita wrote: >> You can use the maven-jar-plugin's test-jar goal: >> https://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html >> >> That creates a second jar with the same coordinates but a 'test' classifier >>

[ANN] Apache Maven Resources Plugin 3.0.2 Released

The Maven team is pleased to announce the release of the Apache Maven Resources Plugin, version 3.0.2 The Resources Plugin handles the copying of project resources to the output directory. There are two different kinds of resources: main resources and test resources. The difference is

Re: ${project.parent.parent.version} does not work

Am 12/05/16 um 21:51 schrieb Florian Schätz: > shared-core pom.xml (pom) > - shared-core module1 pom.xml (jar) > - shared-core module2 pom.xml (jar) > - application1 parent pom.xml (pom) > - application 1 module 1 pom.xml (jar) > - application 1 module 2 pom.xml (jar) > -

Re: ${project.parent.parent.version} does not work

Am 12/05/16 um 21:51 schrieb Florian Schätz: > Hello, > > On 05/12/2016 21:37, Christian Schulte wrote: > >> Only way to get at that would be to declare a property in that >> grandparent's POM. The parent/child hierarchies really are used in the >> opposite way. You

Re: ${project.parent.parent.version} does not work

Am 12/05/16 um 20:33 schrieb Florian Schätz: > ${project.parent.version} directly instead? But > unfortunately, I don't need the parent version, but the grand parent > version and I don't see a way to get it this way... Only way to get at that would be to declare a property in that

Re: ${project.parent.parent.version} does not work

Am 05.12.2016 um 15:09 schrieb Robert Patrick: > Right, it looks at versions to try to find the latest version number. > > Another way that you might solve the problem is simply by chaining > properties. In any one of the parent hierarchy POMs, set > ... and then in the module POM, > just

Re: ${project.parent.parent.version} does not work

Am 12/02/16 um 21:14 schrieb Florian Schätz: > And this I can't see a way to store the grandparent version in a > property via a ${project.version}, because every child will override it For now, you can make that property a constant in the

Re: Structuring bigger Maven projects

Am 12/01/16 um 10:02 schrieb João Cabrita: [...] > Each of the applications live in a separate repository [...] > The libraries also have a repository each [...] That's due to the SCM in use. Yes. This is something to keep in mind as well. What can be one (big) repository using subversion,

Re: Structuring bigger Maven projects

Am 11/30/16 um 19:18 schrieb Florian Schätz: >> A library project to be >> shared between multiple applications each having its own release-cycle >> should not be part of a multi-module project used to build such an >> application and should be an independent project with its own >> release-cycle.

Re: Structuring bigger Maven projects

Am 30.11.2016 um 15:06 schrieb Florian Schätz: > Deployment should be automatic, not requiring many steps, but obviously > it gets a little bit complicated since, for example, when we want to > release an RC1, we would also (preferably) automatically release an RC1 > of the shared code modules

Re: Layered BOMs and overriding dependency management

Am 11/03/16 um 22:55 schrieb Dave Syer: >> Without having to update/change any poms? > > Yes. Remember the Spring Cloud AWS BOM already had the exclusion in it (it > just didn't do anything without using a patched version of Maven). > So you'd say that your patched 3.4.0-SNAPSHOT (model

Re: Layered BOMs and overriding dependency management

Am 11/03/16 um 18:54 schrieb Dave Syer: >> Could you build a 3.4.0-SNAPSHOT locally for testing not requiring a >> model version bump? It's easy. You just need to change method >> 'isGreaterOrEqual' of class 'ModelVersions' to always return 'true'. > > Yes that works - the Wiremock version is

Re: Layered BOMs and overriding dependency management

Am 11/03/16 um 17:14 schrieb Dave Syer: >> Using current 3.4.0-SNAPSHOT master you can set the model version to >> 4.1.0 and then you can use excludes in the dependency management import. >> Would that solve the issue for you? Could you give that a quick test? > > It's not "a quick test",

Re: Layered BOMs and overriding dependency management

Am 11/03/16 um 15:57 schrieb Dave Syer: > I would like to be able to write a BOM and tell Maven that for some > dependencies, I am aware of a conflict in the dependency management, but the > conflict arises in a library I don't control, and I know with high > confidence that my users either a)

Re: [EXTERNAL] Re: help with version range

Am 09/24/16 um 04:16 schrieb Justin Georgeson: > I tried these four version ranges with the 3.4.0-SNAPSHOT from your link > > [1.1.min,1.1.max] > [1.1.*] > [1.2.min,1.2.max] > [1.2.*] > > All four downloaded the expected parent POM without the warnings. That's expected behaviour. Damn it ;-)

Re: [EXTERNAL] Re: help with version range

Am 09/24/16 um 02:15 schrieb Justin Georgeson: > The Aether doc shows both bounds being inclusive with the min/max form, but > you have an exclusive upper bound. Using "[1.1.min,1.1.max]" is working for > me with both 3.2.5 and 3.3.9. So that's awesome! The .* form is working for > me too. I'm

Re: [EXTERNAL] Re: help with version range

Am 09/24/16 um 00:23 schrieb Robert Patrick: > That one is even worse, pom parsing fails... > > [ERROR] [ERROR] Some problems were encountered while processing the POMs: > [ERROR] 'dependencies.dependency.version' for myproject:util:jar must not > contain any of these characters \/:"<>|?* but

Re: [EXTERNAL] Re: help with version range

Am 09/23/16 um 23:38 schrieb Robert Patrick: > This is nice, but it doesn’t work in Maven 3.3.9... > > [ERROR] org.apache.maven.project.artifact.InvalidDependencyVersionException: > Invalid version: [0.8.min,0.8.max] found for: Dependency: myproject:util in > project:

Re: [EXTERNAL] Re: help with version range

Am 09/23/16 um 23:07 schrieb Robert Patrick: > There is already a syntax to give you pre-release versions, right? According > to > https://maven.apache.org/ref/3.3.9/maven-artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html, > the range [1.0,2.0-SNAPSHOT] will give you

Re: POM Model version 4.1.0 in 3.4.0-SNAPSHOTs

Am 24.08.2016 um 19:05 schrieb Curtis Rueden: > One nuance I do not discuss is how importing a BOM under the new scheme now > resolves all version properties, such that overriding them in the consuming > POM has no effect anymore. I still feel this is a bug (or at least > undesired quality) of the

Re: dependencyManagement BOM question

Am 08/23/16 um 21:27 schrieb David Hoffer: > I have some questions regarding how importing a pom type dependency in my > dependencyManagement section really works (e.g. BOM dependency). At a > basic level I understand it will effectively add all its dependencies > defined in its

Re: POM Model version 4.1.0 in 3.4.0-SNAPSHOTs

Am 08/21/16 um 16:35 schrieb Christian Schulte: > There is no other proposal I can make. Call the new behaviour 'include' scope and both scopes could co-exist. I forgot the name of that person who said it's not possible to introduce a new scope in 3.4.0 :-) Regards, -- Christ

Re: POM Model version 4.1.0 in 3.4.0-SNAPSHOTs

Am 08/21/16 um 14:36 schrieb Robert Scholte: > Hi, > > Keep in mind that Maven is not the only tool/application using the pom.xml. Do they implement the import scope feature themselves? > Some of them probably never check the xsd or the modelVersion, so we need > to be very carefull with

Re: POM Model version 4.1.0 in 3.4.0-SNAPSHOTs

Am 08/21/16 um 00:30 schrieb Mark Derricutt: > Christian, is there anywhere describing what changes there are/or planned > in Model version 4.1.0 at all? Nothing is documented yet. There have never been any plans. It's more about having to revert a bunch of useful things to stay backwards

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/19/16 um 17:53 schrieb Curtis Rueden: > Hi Christian, > > This is awesome. > > > == What works == > > With model version 4.0.0, Maven 3.4.0 now behaves exactly as before. And > the property overriding bug no longer occurs, either. This maintains build > reproducibility for my projects,

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/17/16 um 22:16 schrieb Curtis Rueden: > One question: for POM hierarchies with mixed model versions -- a 4.0.0 POM > which imports or extends a 4.1.0 POM or vice versa -- do you foresee any > complications? Parent and child need to use the same model version. There is no way to support

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/17/16 um 04:09 schrieb Mark Derricutt: > On 17 Aug 2016, at 12:32, Christian Schulte wrote: > >> There is an easy way to solve this. Maven validates the model version in >> the POM to match "4.0.0". Based on that version, Maven can decide how to >> behav

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/16/16 um 23:14 schrieb Curtis Rueden: > properly with Maven 3.4.0. But I am very concerned about the precedent > here: at any point in the future, complex builds which used to work might > stop doing so, even without a major version increment, due to future > changes in the logic of core

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/15/16 um 20:49 schrieb David Hoffer: > I will try to test with 3.2.2 but I can confirm that 3.2.5 does not have > this behavior as that is our official build version for this application. > I am trying to move to latest maven version and discovered this. A project to reproduce this would be

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/15/16 um 20:30 schrieb David Hoffer: > I'm testing with build 110 and have found an error with one of our current > builds (it works through 3.3.9). It's a bit of an odd-ball case. > > We have a child parent pom module that has several children if its own. > One of those child modules uses

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/12/16 um 15:58 schrieb Samuel Langlois: > Thanks for your answer Robert. > It is a bit more complicated than just being unable to override a property. > It's more that you can't change a dependencyManagement defined above by > overriding a property. > Anyway, I think it deserves an issue to

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Could you please test properties can correctly be overridden again in the latest 3.4.0-SNAPSHOT available from . It should have been fixed by this commit

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

The code in question is in class 'DefaultModelBuilder'. Everything is done by those two methods: public ModelBuildingResult build( ModelBuildingRequest request ) public ModelBuildingResult build( ModelBuildingRequest request, ModelBuildingResult result ) Called in that order.

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/13/16 um 00:28 schrieb Christian Schulte: > reviewing things. So current state of this is: "That's the behaviour > requested and tested during commiting to MNG-5971. Cannot override > properties? Really requested behaviour? Maybe incorrect. Need to look at > it again. T

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/12/16 um 20:11 schrieb Curtis Rueden: > Hi Christian, > > Thank you very much for looking at my example, and your speedy reply. > >> Can you please add your objections to MNG-5971 in JIRA. > > Done. I also added the same comments to MNG-6079, which I believe is a > legitimate regression

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 12.08.2016 um 19:16 schrieb Curtis Rueden: Hi all, Concerned by this thread, I did some tests. And I have to say, the new Maven 3.4.0 dependency resolution rules seem like a step backwards. == REAL-WORLD EXAMPLE == Consider the following project:

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Can you please add your objections to MNG-5971 in JIRA. Maybe by copy and pasting your email. Reverting to the old behaviour is problematic and most of the users having taken part in that discussion will disagree with you, I think. The issue has been filed due to real-world problems. There are

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 08/12/16 um 14:41 schrieb Samuel Langlois: > Hello > > I noticed a change of behaviour in Maven 3.4, which made one of our builds > fail. > It may be a bit of a corner case, so I'll let someone else decide whether > it's a regression or a bug fix... You can read all about it here:

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 07/24/16 um 19:25 schrieb Dan Tran: > Yes, I need to override the original import with 'optional' set to false. > At the same time, i file a bug with spring to see if it is intentional > This is what I would do as well. If the majority of users will never need that dependency and it is not

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 07/24/16 um 09:32 schrieb Dan Tran: > yes, found this > > > com.googlecode.json-simple > json-simple > ${simple-json.version} > true > > > at sprint-boot-dependencies-1.2.8's dependencyManagement. This may be a > bug of the BOM. Not sure why it is set as optional and it is the only one >

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 07/23/16 um 23:41 schrieb Dan Tran: > Looks good on my 170 modules with Takari's smart builder build. Except > one module with one transitive dependency disappears and causes compilation > error. > > Any suggestion how to troubleshoot is very much reproducible build failure? Could be caused

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 07/06/16 um 15:08 schrieb Jason van Zyl: > Feature toggles, as the practice has been for many years, has the user being > conscious of what they are doing. The feature may prove to be a problem and > you specifically don’t want to expose it to the whole user population. I > honestly find

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 07/03/16 um 01:49 schrieb Christian Schulte: > Am 07/03/16 um 01:39 schrieb Karl Heinz Marbaise: >> Hi, >> >> On 7/3/16 1:31 AM, Christian Schulte wrote: >>> Am 07/02/16 um 23:18 schrieb Karl Heinz Marbaise: >>>> Hi, >>>> >>>> O

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 07/03/16 um 01:39 schrieb Karl Heinz Marbaise: > Hi, > > On 7/3/16 1:31 AM, Christian Schulte wrote: >> Am 07/02/16 um 23:18 schrieb Karl Heinz Marbaise: >>> Hi, >>> >>> On 7/2/16 2:06 PM, Jason van Zyl wrote: >>> >>> >S

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 07/03/16 um 01:42 schrieb Karl Heinz Marbaise: > Hi, > > On 7/3/16 1:34 AM, Christian Schulte wrote: >> Am 07/03/16 um 01:16 schrieb Karl Heinz Marbaise: >>> If we make the decision to make a particular feature the default we can >>> simple remove it from th

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 07/03/16 um 01:16 schrieb Karl Heinz Marbaise: > If we make the decision to make a particular feature the default we can > simple remove it from the feature toggle list...Or we can make to > produce it warnings etc. And how is that different from just shipping that feature active by default

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 07/02/16 um 23:18 schrieb Karl Heinz Marbaise: > Hi, > > On 7/2/16 2:06 PM, Jason van Zyl wrote: > > >So we need to figure out a way to deliver the new behavior while > preserving > >the old for a time being. Maybe a branch, > > > > but I think the best way to do it is to have both

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 07/02/16 um 23:18 schrieb Karl Heinz Marbaise: > Hi, > > On 7/2/16 2:06 PM, Jason van Zyl wrote: > > >So we need to figure out a way to deliver the new behavior while > preserving > >the old for a time being. Maybe a branch, > > > > but I think the best way to do it is to have both

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 07/02/16 um 23:18 schrieb Karl Heinz Marbaise: > Hi, > > On 7/2/16 2:06 PM, Jason van Zyl wrote: > > >So we need to figure out a way to deliver the new behavior while > preserving > >the old for a time being. Maybe a branch, > > > > but I think the best way to do it is to have both

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 07/02/16 um 15:53 schrieb Jeff Jensen: > Feature toggles +1 FTW > > Agreed, switching the default behavior over time is a good path of change. > Perhaps helping with the awareness of the feature, when the feature is off, > display an info message stating this feature exists and suggest

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 07/02/16 um 12:36 schrieb Oliver B. Fischer: > My suggestions is based on the view of a Maven user who would like to do > it's daily job ;-) > > In our team we have > 20 Maven projects and as a Maven 'User' you need > the chance to fix such issues before the break your build. Everyone >

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 06/20/16 um 22:00 schrieb Oliver B. Fischer: > Yes, I think this would be very helpfull. Otherwise I see a lot of > people complaining about Maven and that is not able to do its work. Such warning messages could only be issued by Aether. That cannot be done in 3.4. We already reverted the

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 2)

http://git-wip-us.apache.org/repos/asf/maven/commit/ded1379e - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 2)

Am 06/14/16 um 18:46 schrieb Anton Tanasenko: > Christian? Anyone? > > 2016-06-13 1:19 GMT+03:00 Anton Tanasenko : > >> I've tried running m2eclipse tests with 3.4.0-SNAPSHOT maven. There are >> several failures. >> >> 1. src/x/resources-filtered addition, which we will

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 06/12/16 um 23:03 schrieb Mirko Friedenhagen: > So maybe I got all scopes wrong, Yes. And that's the reason those bugfixes in Maven have been reverted latetly. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 06/12/16 um 22:01 schrieb Oliver B. Fischer: > With this snapshot I am unable to build jQAssistant. You can fetch it > from g...@github.com:buschmais/jqassistant.git > You need to fix the project. 3.4 adds support for managing the 'optional' flag in dependency management and contains

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 06/12/16 um 21:47 schrieb Mirko Friedenhagen: > Hello Christian, > > that I could fix. Although hamcrest is transitive in junit. It is a 'compile' scope dependency of 'junit' and that is transitive and will become 'test' in case of using 'junit' in 'test' scope. If you manage that dependency

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

Am 06/12/16 um 00:03 schrieb Mirko Friedenhagen: > Hello Karl-Heinz, > > I tried this with 2 projects, firstly an inhouse project and it choked with: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19:test > (default-test) on project ui-mamido-qamove:

Re: Maven JAXB

Don Hosek schrieb: groupIdjaxb/groupId That groupId seems wrong. plugin groupIdcom.sun.tools.xjc.maven2/groupId artifactIdmaven-jaxb-plugin/artifactId version1.1/version /plugin -- Christian

Re: Creating a zip of non-java files

Doug Hughes schrieb: If there's any documentation you can recommend on how to do this, that'd be great. I'm really just getting started with Maven and I'm using it for a fairly non-standard language. As such, the learning curve is a bit steep. Thanks, Maybe something like this ?

Re: Newbie - Can't resolve artifact.

KurtG schrieb: This should look familiar --- [INFO] Failed to resolve artifact. No versions are present in the repository for the artifact with a range [2.1,) commons-collections:commons-collections:jar:null from the specified remote repositories: central

Re: Up-to-date release

sverhagen schrieb: Hi. We heavily use the Maven release plugin. Following scenario: * Developers update from SVN * Developer 1 commits a change * Developer 2 commits a change and releases (mvn release:prepare) Because developer 2 does not explicitly update from SVN, the change from

Re: Execution of the *.jar-File after successful building of package possible?

Ulrich Wolf wrote: Hello, when I build my project with the goal package I get a *.jar-File, which I have to execute manually after the compilation packaging. Is there any way to automatically execute this file directly after maven has completed this task? The exec-maven-plugin can do

Re: Does Java 1.4 support maven-jaxb-plugin?

thomas2004 wrote: Surely when I use Java 1.5. It is OK. But I do want to use Java 1.4 since I will deploy my web-application to WebLogic 8 which is just compatible with Java 1.4. Has someone idea? The plugin you use is for JAXB 2.x which requires you to use at least java 1.5. For java 1.4

Re: [PLEASE TEST] Maven 2.1.0-M1-RC13

Martin Höller wrote: Hi! On Thursday 04 September 2008 John Casey wrote: On the last go around, we had one issue pop up with maven plugin builds (though it might also apply to build extensions in the reactor as well). I've fixed it, and now here's the lucky 13th release candidate:

Re: Preflight check for 2.0.7

On Di, Juni 5, 2007 01:08, Jason van Zyl wrote: I have built a snapshot for 2.0.7 and put it here: http://people.apache.org/~jvanzyl/ I figure folks are going to try and squeeze in more issues so what I plan is let people state their case for issues and I'll slot those into 2.0.8. I'll

Re: Preflight check for 2.0.7

On Do, Juni 7, 2007 15:20, Jason van Zyl wrote: What version of the site plugin? :~$ rm -rf ~/.m2/repository/ :~$ mvn clean install -U -up Stacktrace omitted. :~$ ls -lah ~/.m2/repository/org/apache/maven/plugins/maven-site-plugin/ insgesamt 24K drwxr-xr-x 3 schulte schulte 4,0K 2007-06-07

[m2] Release plugin in subversion repository broken ?

Hi, I just wanted to make a release and cannot get the release plugin do the job as it once did 8-(. Since yesterday I need to apply the attached patch to make it run without throwing a ClassCastException. What drives me crazy is that the rewriting of the poms does not work anymore. It does

[m2] Howto custom CharsetProvider implementations ?

Hi, I have a problem with unit testing custom charset provider implementations. In some module I have a src/main/resources/META-INF/services/java.nio.charset.spi.CharsetProvider file defining custom charsets implemented in the same module. The jar file produced with this module works outside of

[m2] dependencyManagement question ?

Hi, I have a question regarding the dependencyManagement section in the pom.xml files. When I have several dependencies and there are conflicts in the transitive dependencies (e.g. commons-beanutils-1.6.1 and commons-beanutils-1.7.0) I thought I could specifiy the version to use in the

What happened to svn.codehaus.org ?

I cannot connect to svn.codehaus.org since a few days. Did the subversion repository of mojo.codehaus.org change ? ~# ping svn.codehaus.org PING beaver.codehaus.org (64.7.141.17) 56(84) bytes of data. From beaver.codehaus.org (64.7.141.17) icmp_seq=1 Destination Port Unreachable From

Re: What happened to svn.codehaus.org ?

Brett Porter schrieb: It's working for me now. The ping result below is normal. The host was reached, but the port was rejected. - Brett Ups. It works externally. So we have network problems internally. Sorry. -- Christian

[m2] Howto access configurations of mojos in a multi-module build ?

Hi, I would like to extend the maven-javadoc-plugin to automatically create offline links to the modules within a multi-module build. It could work if all modules would use the same configuration of the plugin. How would I access the configuration of the javadoc-plugin inside the plugin

Re: Multiple JDKs ?

Emmanuel Venisse schrieb: Not yet, it wil be supported in 1.1. http://jira.codehaus.org/browse/CONTINUUM-44 Emmanuel Thanks. -- Christian

Re: [m2] [evangelism] [suggestion] New libraries coming out

Alexandre Poitras schrieb: Nah only correcting errors. Lot of POMs are invalid right now. Ah ok. So fixing a pom which did not work before... -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional

Multiple JDKs ?

Hi, is it possible to make continuum build with different JDKs ? I imported multiple maven 2 projects and need some of them to be build with an IBM JDK and the others with Sun. Is it supported ? -- Christian

Re: [m2] [evangelism] [suggestion] New libraries coming out

Arik Kfir schrieb: Hi, Sorry for butting in - but how about adding some (willing) people as administrators of *parts* of the ibiblio repo? I for example wouldn't mind being responsible for managing, say, the jboss section. This means that the admin only has permissions for that particular

[m2] Multiple source roots ?

Hi, how do I add multiple source roots to the compiler plugin for compilation ? I have a problem with a plugin which does not make the appropriate project.addCompileSourceRoot() calls after generating sources. What I need is some kind of workaround to get the generated sources added to the

Re: [m2] Multiple source roots ?

dan tran schrieb: write your own plugin to add them in. -D Thats what I wanted to avoid but I did exactly that 8-) -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL

[m2] Rreproducibility best-practices ?

Hi, how does Maven 2 implement reproducibility ? Say a release is tagged in CVS. I want this tag to build *exactly* the same JARs, WARs and EARs with exactly the same dependencies. What happens, if e.g. because of a bugfix in maven some artifacts are resolved differently ? So the question

[m2] Schedule for 2.0.1 ?

Hi, is there any planned release date for 2.0.1 or maybe some release candidate ? -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] Downloading source-code jar files ?

Jochen Wiedmann schrieb: Henry Isidro wrote: Try this: dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1-sources/version typejar/type scopeprovided/scope /dependency /dependencies If you are using the Eclipse plugin, then a more

[m2] Deplyoment into different repository ?

Hi, I want to deploy some aritfacts into our internal development repository. Currently I have to edit every POM to point the distributionMnagement-Section to the correct repository. Is it possible to deploy without changing the pom ? E.g. I need to provide current snapshots of maven 2 and

Re: [m2] Avoiding duplicate jar files in a generated ear file ?

Christian Schulte schrieb: Hi, when I build an ear file with maven 2 it happens that because of transitive dependencies I get e.g. two struts.jar files in the generated file. What is the recommended way of managing transitive dependencies ? Say I have a dependency which itself has

[m2] Downloading source-code jar files ?

Hi, how do I make maven fetch e.g. junit-3.8.1-sources.jar so that this file gets copied into the local repository ? I tried putting a dependency to it in the root pom like this dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version

Re: [m2] Avoiding duplicate jar files in a generated ear file ?

Jörg Schaible schrieb: Christian Schulte wrote on Monday, December 05, 2005 12:13 PM: Christian Schulte schrieb: Hi, when I build an ear file with maven 2 it happens that because of transitive dependencies I get e.g. two struts.jar files in the generated file. What is the recommended way

How to get a copy of the repository ?

Hi, I would like to have a local copy of some of the components in the remote repository at http://www.ibiblio.org/maven2. Is there an easy way to get a local copy of this ? I tried rsync but it seems ibiblio does not support rsync. Is the repository also available via ftp ? -- Christian

Re: How to get a copy of the repository ?

Christian Schulte schrieb: Hi, I would like to have a local copy of some of the components in the remote repository at http://www.ibiblio.org/maven2. Is there an easy way to get a local copy of this ? I tried rsync but it seems ibiblio does not support rsync. Is the repository also

[m2] Roadmap ?

The Maven 1.x site has a link to a planned roadmap. What is the roadmap for Maven 2.x ? -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] Roadmap ?

Stephane Nicoll schrieb: http://jira.codehaus.org/browse/MNG?report=com.atlassian.jira.plugin.system.project:roadmap-panel Thanks. Did not know about that. -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For

Re: [m2] spring-1.2.6 poms ?

Carlos Sanchez schrieb: On 11/29/05, Christian Schulte [EMAIL PROTECTED] wrote: Hi, I do not understand how transitive dependencies are supposed to work. Why are there no poms for spring 1.2.6 but for 1.2.5 ? Because it takes time to do them Sorry. I did not notice that 1.2.6

[m2] Javadoc report with incorrect index.html page ?

Hi, what may be the reason why the index.html at target/site/apidocs is the same as the index.html of the project/module. The javadoc is generated but the index.html inside target/site/apidocs is wrong. I know it worked a few days ago but now stopped working and I cannot find the mistake in

Re: [m2] Javadoc report with incorrect index.html page ?

Brett Porter schrieb: bug in the last release, fixed in SVN, release coming up soon. More info in JIRA or the archives. Thanks for the info. -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,

Re: [m2] What happened to 'maven dist' ?

Wendy Smoak schrieb: On 11/27/05, Brett Porter [EMAIL PROTECTED] wrote: Yep! http://maven.apache.org/plugins/maven-assembly-plugin/howto.html $ mvn assembly:assembly -Dmaven.assembly.descriptorId=src [ERROR] BUILD FAILURE [INFO] --- ---

Re: [m2] Javadoc report with incorrect index.html page ?

Brett Porter schrieb: bug in the last release, fixed in SVN, release coming up soon. More info in JIRA or the archives. Is there some info on how to build a maven2 snapshot correctly ? I have build a snapshot by checking out trunk and doing a ./bootstrap.sh. So I have a maven-2.0.1-SNAPSHOT

Re: [m2] Javadoc report with incorrect index.html page ?

Christian Schulte schrieb: Brett Porter schrieb: bug in the last release, fixed in SVN, release coming up soon. More info in JIRA or the archives. Is there some info on how to build a maven2 snapshot correctly ? I have build a snapshot by checking out trunk and doing a ./bootstrap.sh. So

[m2] spring:spring, springframework:spring or org.springframework:spring ?

Hi, what are the correct dependencies to use for the spring framework ? There exist several. -- Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[m2] Why does DefaultModelInheritanceAssembler ignore relativePath../relativePath or module...module definitions ?

Hi, I have severe problems with the flat project layout as described at http://maven.apache.org/guides/mini/guide-ide-eclipse.html at the end of the site. As it seems inheritance is not supporting the relative path and modules settings. Somewhere in here

  1   2   >