|
»
»
»
[2.0.9 RC6] Release Candidate testing
|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
 |
[2.0.9 RC6] Release Candidate testing
by Brian E Fox
::
Rate this Message:
I didn't get much response yesterday and we respun a new RC (RC6) so I'm
resending the original mail. If nothing turns up within 3 days, then we will restage and vote for a release. Thanks, Brian --------------------------------------- In an attempt to raise quality and reduce/eliminate regressions in the core releases, we are experimenting with a new release process. The old process had a few informal staged builds followed by one or more official staged builds that where voted on. Clearly this didn't attract enough testing prior to the official release to identify regressions or other major issues. The new process we are using for the 2.0.9 release is to cut actual release candidate (RCx) releases. These are released with the normal release process so it generates a tag, but do not get sync'd to central. We have gone through several RCs[1] as we tested on the dev@ list. The next step is to open it up to the user list for fix validation and regression identification. This is really the first time we've followed such a process so we'll have to see how it pans out. Here are the "operating parameters" for this test: * The goal of the RCs are to stabilize the release and any changes at this point naturally risks further regressions. Therefore, the list of fixes for 2.0.9 is locked. We will not be including any more fixes at this point unless it meets the requirements laid out below. This means please don't reply with "could you just include xyz". * The issues we are looking to identify and fix are those where it can be shown to work with 2.0.8, but not with 2.0.9-RCxxx. These issues we will almost certainly fix. Our goal is to fix ALL regressions identified between 2.0.8 and 2.0.9, but naturally we need to weigh the severity of the issue along with the exposure against the complexity and risk of further regressions by fixing it. * If any of the issues that are marked as fixed for 2.0.9 are found to not be fixed, then we are interested in this as well, but more likely than not the fix will be rolled back and rescheduled for 2.0.10. Naturally the importance of the issue has bearing in how this will be handled. * If we can receive a sample project or IT[2] showing the issue, then it increases the likelihood of a quick fix and turnaround of the RC exponentially, both for regressions and for "not fixed" issues in 2.0.9 * Please report any regressions found between earlier versions of 2.0.x and 2.0.9 as they will be prioritized for 2.0.10 along with anything rolled back / not fixed from 2.0.9 * We will continue to iterate through this process until we feel that the release is ready to go. User list input will have a large factor in making this decision. That said, the quality of the 2.0.9 release will depend on the level of involvement from the entire community to test, reproduce and report issues identified. * Please file a Jira[3] for anything you find, and then reply to the RC thread with the details and issue number so that others may see and reduce duplicate reports. We will be watching Jira closely for reports with 2.0.9 in the affected version. * Once a release is ready, we will rebuild and restage the code from the most recent RC for a formal vote. This will produce the official "2.0.9" release. The list of issues fixed for this release can be found here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13801&styleName =Html&projectId=10500&Create=Create Some notable changes are: * Plugin versions are locked in the superpom. (MNG-3395) You can see the locked versions here: http://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/ma ven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml * In most cases they are locked to the currently available plugin to avoid suddenly downgrading users that haven't locked their own versions (still the best practice). * Webdav is included in the core, meaning you can deploy:deploy-file without a pom to include the extension (if you use webdav obviously) (MNG-2664) * New syntax for mirror definitions. Details here: MNG-3461 * Introduction of Import scope: (MNG-3220) http://maven.apache.org/guides/introduction/introduction-to-dependency-m echanism.html#Importing_Dependencies The binaries for this RC can be found here: http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/ (naturally take the highest RC number deployed as it will change when we iterate) [1] Previous RC threads: http://www.nabble.com/-Pre-Vote--release-maven-2.0.9-td16124759s177.html http://www.nabble.com/-pre-vote-take-3--2.0.9-RC3-td16314473s177.html http://www.nabble.com/-2.0.9-RC4--td16344067s177.html http://www.nabble.com/-2.0.9-RC5--td16365465s177.html#a16365465 [2] Creating a Core IT: http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test [3] http://jira.codehaus.org/browse/MNG Thanks, The Maven Team |
|
|
Re: [2.0.9 RC6] Release Candidate testing
by Dan Tran
::
Rate this Message:
no issue found on my build
-D On Tue, Apr 1, 2008 at 2:34 PM, Brian E. Fox <brianf@...> wrote: > I didn't get much response yesterday and we respun a new RC (RC6) so I'm > resending the original mail. If nothing turns up within 3 days, then we > will restage and vote for a release. > > > > Thanks, > > Brian > > > > --------------------------------------- > > > > In an attempt to raise quality and reduce/eliminate regressions in the > core releases, we are experimenting with a new release process. The old > process had a few informal staged builds followed by one or more > official staged builds that where voted on. Clearly this didn't attract > enough testing prior to the official release to identify regressions or > other major issues. > > > > The new process we are using for the 2.0.9 release is to cut actual > release candidate (RCx) releases. These are released with the normal > release process so it generates a tag, but do not get sync'd to central. > We have gone through several RCs[1] as we tested on the dev@ list. The > next step is to open it up to the user list for fix validation and > regression identification. This is really the first time we've followed > such a process so we'll have to see how it pans out. > > > > Here are the "operating parameters" for this test: > > > > * The goal of the RCs are to stabilize the release and any changes at > this point naturally risks further regressions. Therefore, the list of > fixes for 2.0.9 is locked. We will not be including any more fixes at > this point unless it meets the requirements laid out below. This means > please don't reply with "could you just include xyz". > > > > * The issues we are looking to identify and fix are those where it can > be shown to work with 2.0.8, but not with 2.0.9-RCxxx. These issues we > will almost certainly fix. Our goal is to fix ALL regressions identified > between 2.0.8 and 2.0.9, but naturally we need to weigh the severity of > the issue along with the exposure against the complexity and risk of > further regressions by fixing it. > > > > * If any of the issues that are marked as fixed for 2.0.9 are found to > not be fixed, then we are interested in this as well, but more likely > than not the fix will be rolled back and rescheduled for 2.0.10. > Naturally the importance of the issue has bearing in how this will be > handled. > > > > * If we can receive a sample project or IT[2] showing the issue, then > it increases the likelihood of a quick fix and turnaround of the RC > exponentially, both for regressions and for "not fixed" issues in 2.0.9 > > > > * Please report any regressions found between earlier versions of > 2.0.x and 2.0.9 as they will be prioritized for 2.0.10 along with > anything rolled back / not fixed from 2.0.9 > > > > * We will continue to iterate through this process until we feel that > the release is ready to go. User list input will have a large factor in > making this decision. That said, the quality of the 2.0.9 release will > depend on the level of involvement from the entire community to test, > reproduce and report issues identified. > > > > * Please file a Jira[3] for anything you find, and then reply to the > RC thread with the details and issue number so that others may see and > reduce duplicate reports. We will be watching Jira closely for reports > with 2.0.9 in the affected version. > > > > * Once a release is ready, we will rebuild and restage the code from > the most recent RC for a formal vote. This will produce the official > "2.0.9" release. > > > > The list of issues fixed for this release can be found here: > > http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13801&styleName > =Html&projectId=10500&Create=Create > > > > Some notable changes are: > > * Plugin versions are locked in the superpom. (MNG-3395) You can see > the locked versions here: > > http://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/ma > ven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml > > > > * In most cases they are locked to the currently available plugin to > avoid suddenly downgrading users that haven't locked their own versions > (still the best practice). > > > > * Webdav is included in the core, meaning you can deploy:deploy-file > without a pom to include the extension (if you use webdav obviously) > (MNG-2664) > > > > * New syntax for mirror definitions. Details here: MNG-3461 > > > > * Introduction of Import scope: (MNG-3220) > > http://maven.apache.org/guides/introduction/introduction-to-dependency-m > echanism.html#Importing_Dependencies > > > > > > The binaries for this RC can be found here: > > http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa > che-maven/ > > (naturally take the highest RC number deployed as it will change when we > iterate) > > > > [1] Previous RC threads: > > > http://www.nabble.com/-Pre-Vote--release-maven-2.0.9-td16124759s177.html > > http://www.nabble.com/-pre-vote-take-3--2.0.9-RC3-td16314473s177.html > > http://www.nabble.com/-2.0.9-RC4--td16344067s177.html > > http://www.nabble.com/-2.0.9-RC5--td16365465s177.html#a16365465 > > > > [2] Creating a Core IT: > > http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test > > > > [3] http://jira.codehaus.org/browse/MNG > > > > > > Thanks, > > The Maven Team > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: [2.0.9 RC6] Release Candidate testing
by matinh
::
Rate this Message:
On 01 Apr 2008, Brian E. Fox wrote:
> I didn't get much response yesterday and we respun a new RC (RC6) so I'm > resending the original mail. Do you also want feedback like "no problems here"? If yes: 2.0.9-RC6 runs fine, no problems here :-) hth, - martin |
|
|
RE : [2.0.9 RC6] Release Candidate testing
by Deneux, Christophe
::
Rate this Message:
+1, no problem to build my projects -- Christophe ________________________________ De: Martin Hoeller [mailto:martin@...] Date: mer. 02/04/2008 09:06 À: users@... Objet : Re: [2.0.9 RC6] Release Candidate testing On 01 Apr 2008, Brian E. Fox wrote: > I didn't get much response yesterday and we respun a new RC (RC6) so I'm > resending the original mail. Do you also want feedback like "no problems here"? If yes: 2.0.9-RC6 runs fine, no problems here :-) hth, - martin This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. |
|
|
|
|
|
Re: SV: [2.0.9 RC6] Release Candidate testing
by John Casey-5
::
Rate this Message:
Do you have a failing POM/project we could use to express this
problem for the purposes of debugging? It looks like the differences in dependency ordering (precedence of plugin-level dependencies in your POM, in this case) may be affecting your build, but I can't be sure without something live to look at. If you feel like it, it would be great to have a JIRA issue for this problem. If you create it, you can participate in any ongoing discussion related to its debugging/solution...otherwise, if I create it, I can post the issue # here... But in any case, a failing test build would be a great help. If you don't have a full build you could send us, then perhaps a detailed description of your usage of the plugin, along with the captured output from running in debug mode (with the -X command-line option specified)...this would also be a great help. Thanks, -john On Apr 2, 2008, at 11:38 AM, Arne Rivenes wrote: > I get errors with 2.0.9-RC6 and org.codehaus.mojo.jaxb2-maven-plugin. > The same occurs with 2.0.9-RC3, but the exact same build works with > Maven 2.0.8. > I've tested with jaxb2-plugin 1.0.2 and 1.0.1 > > The only thing that's changed are the M2_HOME variable that I use > in the > path. > > This is on Windows XP2 with java 5. It also fails with java 6. > > I use org.jvnet.jaxb2.maven2.maven-jaxb2-plugin in another project. > That one seems to work. > > I realize that both these plugins are outside of the > org.apache.maven.plugins, but still you might want to know. > > Build log below. > > [INFO] [jaxb2:xjc {execution: xjc-soa-xsdcontrol}] > [INFO] Generating source... > [INFO] parsing a schema... > [FATAL ERROR] org.codehaus.mojo.jaxb2.XjcMojo#execute() caused a > linkage > error (java.lang.NoSuchMethodError) and may be out-of-date. Check the > realm > > [FATAL ERROR] Plugin realm = > app0.child-container[org.codehaus.mojo:jaxb2-maven-plugin] > urls[0] = > file:/c:/dev/maven-local-repo/org/codehaus/mojo/jaxb2-maven-plugin/ > 1.2/j > axb2-maven-plugin-1.2.jar > urls[1] = > file:/c:/dev/maven-local-repo/com/sun/xml/bind/jaxb-impl/2.1/jaxb- > impl-2 > .1.jar > urls[2] = > file:/c:/dev/maven-local-repo/javax/xml/bind/jaxb-api/2.1/jaxb- > api-2.1.j > ar > urls[3] = > file:/c:/dev/maven-local-repo/javax/xml/stream/stax-api/1.0-2/stax- > api-1 > .0-2.jar > urls[4] = > file:/c:/dev/maven-local-repo/javax/activation/activation/1.1/ > activation > -1.1.jar > urls[5] = > file:/c:/dev/maven-local-repo/com/sun/xml/bind/jaxb-xjc/2.0.3/jaxb- > xjc-2 > .0.3.jar > urls[6] = > file:/c:/dev/maven-local-repo/org/codehaus/plexus/plexus-utils/1.1/ > plexu > s-utils-1.1.jar > [FATAL ERROR] Container realm = plexus.core > urls[0] = > file:/C:/dev/maven/apache-maven-2.0.9-RC6/lib/maven-2.0.9-RC6-uber.jar > [INFO] > ---------------------------------------------------------------------- > -- > [ERROR] FATAL ERROR > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] > com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>([Ljava/lang/ > Class;Lja > va/util/Collection;Ljava/lang/String;Z)V > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] Trace > java.lang.NoSuchMethodError: > com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>([Ljava/lang/ > Class;Lja > va/util/Collection;Ljava/lang/String;Z)V > at > com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImp > l. > getJAXBContext(AnnotationParserFactoryImpl.java:80) > at > com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImp > l. > access$000(AnnotationParserFactoryImpl.java:54) > at > com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImp > l$ > 1.<init>(AnnotationParserFactoryImpl.java:103) > at > com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImp > l. > create(AnnotationParserFactoryImpl.java:102) > at > com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.createAnnotationParser > (NGCCRu > ntimeEx.java:320) > at > com.sun.xml.xsom.impl.parser.state.annotation.action0 > (annotation.java:48 > ) > at > com.sun.xml.xsom.impl.parser.state.annotation.enterElement > (annotation.ja > va:68) > at > com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement > (NGCCRunt > ime.java:378) > at > com.sun.xml.xsom.impl.parser.state.NGCCHandler.spawnChildFromEnterElem > en > t(NGCCHandler.java:74) > at > com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java: > 213) > at > com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement > (NGCCRunt > ime.java:378) > at > com.sun.xml.xsom.impl.parser.state.NGCCHandler.revertToParentFromEnter > El > ement(NGCCHandler.java:111) > at > com.sun.xml.xsom.impl.parser.state.foreignAttributes.enterElement > (foreig > nAttributes.java:50) > at > com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement > (NGCCRunt > ime.java:378) > at > com.sun.xml.xsom.impl.parser.state.NGCCHandler.spawnChildFromEnterElem > en > t(NGCCHandler.java:74) > at > com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java: > 436) > at > com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement > (NGCCRunt > ime.java:378) > at > com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java: > 205) > at > com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement > (NGCCRunt > ime.java:378) > at > com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java: > 181) > at > com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement > (NGCCRunt > ime.java:378) > at > com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java: > 372) > at > com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement > (NGCCRunt > ime.java:378) > at > com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java: > 384) > at > com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement > (NGCCRunt > ime.java:378) > at > com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java: > 189) > at > com.sun.xml.xsom.impl.parser.state.NGCCRuntime.startElement > (NGCCRuntime. > java:219) > at > org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527) > at > com.sun.tools.xjc.reader.ExtensionBindingChecker.startElement > (ExtensionB > indingChecker.java:271) > at > org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527) > at > com.sun.tools.xjc.reader.xmlschema.parser.IncorrectNamespaceURIChecker > .s > tartElement(IncorrectNamespaceURIChecker.java:97) > at > org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527) > at > com.sun.tools.xjc.reader.xmlschema.parser.CustomizationContextChecker. > st > artElement(CustomizationContextChecker.java:172) > at > org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527) > at > com.sun.tools.xjc.reader.internalizer.DOMForestScanner > $LocationResolver. > startElement(DOMForestScanner.java:125) > at > com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:224) > at > com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:261) > at > com.sun.xml.bind.unmarshaller.DOMScanner.visit(DOMScanner.java:230) > at > com.sun.xml.bind.unmarshaller.DOMScanner.scan(DOMScanner.java:107) > at > com.sun.tools.xjc.reader.internalizer.DOMForestScanner.scan > (DOMForestSca > nner.java:73) > at > com.sun.tools.xjc.reader.internalizer.DOMForestScanner.scan > (DOMForestSca > nner.java:81) > at > com.sun.tools.xjc.reader.internalizer.DOMForestParser.parse > (DOMForestPar > ser.java:83) > at > com.sun.tools.xjc.ModelLoader$XMLSchemaParser.parse > (ModelLoader.java:237 > ) > at > com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.parseEntity > (NGCCRuntimeEx.jav > a:298) > at > com.sun.xml.xsom.impl.parser.ParserContext.parse(ParserContext.java: > 87) > at com.sun.xml.xsom.parser.XSOMParser.parse(XSOMParser.java: > 147) > at com.sun.xml.xsom.parser.XSOMParser.parse(XSOMParser.java: > 136) > at > com.sun.tools.xjc.ModelLoader.createXSOM(ModelLoader.java:484) > at > com.sun.tools.xjc.ModelLoader.loadXMLSchema(ModelLoader.java:347) > at com.sun.tools.xjc.ModelLoader.load(ModelLoader.java:145) > at com.sun.tools.xjc.ModelLoader.load(ModelLoader.java:91) > at com.sun.tools.xjc.Driver.run(Driver.java:287) > at org.codehaus.mojo.jaxb2.XjcMojo.execute(XjcMojo.java:301) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo > (DefaultPluginMa > nager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals > (Default > LifecycleExecutor.java:558) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif > ec > ycle(DefaultLifecycleExecutor.java:499) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal > (DefaultL > ifecycleExecutor.java:478) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand > le > Failures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment > s( > DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute > (DefaultLifec > ycleExecutor.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.jav > a:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessor > Impl.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: 3 seconds > [INFO] Finished at: Wed Apr 02 17:22:48 CEST 2008 > [INFO] Final Memory: 9M/18M > [INFO] > ---------------------------------------------------------------------- > -- > > Arne. > > -----Opprinnelig melding----- > Fra: Brian E. Fox [mailto:brianf@...] > Sendt: 1. april 2008 23:35 > Til: Maven Users List > Emne: [2.0.9 RC6] Release Candidate testing > > I didn't get much response yesterday and we respun a new RC (RC6) > so I'm > resending the original mail. If nothing turns up within 3 days, > then we > will restage and vote for a release. > > > > Thanks, > > Brian > > > > --------------------------------------- > > > > In an attempt to raise quality and reduce/eliminate regressions in the > core releases, we are experimenting with a new release process. The > old > process had a few informal staged builds followed by one or more > official staged builds that where voted on. Clearly this didn't > attract > enough testing prior to the official release to identify > regressions or > other major issues. > > > > The new process we are using for the 2.0.9 release is to cut actual > release candidate (RCx) releases. These are released with the normal > release process so it generates a tag, but do not get sync'd to > central. > We have gone through several RCs[1] as we tested on the dev@ list. The > next step is to open it up to the user list for fix validation and > regression identification. This is really the first time we've > followed > such a process so we'll have to see how it pans out. > > > > Here are the "operating parameters" for this test: > > > > * The goal of the RCs are to stabilize the release and any > changes at > this point naturally risks further regressions. Therefore, the list of > fixes for 2.0.9 is locked. We will not be including any more fixes at > this point unless it meets the requirements laid out below. This means > please don't reply with "could you just include xyz". > > > > * The issues we are looking to identify and fix are those where > it can > be shown to work with 2.0.8, but not with 2.0.9-RCxxx. These issues we > will almost certainly fix. Our goal is to fix ALL regressions > identified > between 2.0.8 and 2.0.9, but naturally we need to weigh the > severity of > the issue along with the exposure against the complexity and risk of > further regressions by fixing it. > > > > * If any of the issues that are marked as fixed for 2.0.9 are > found to > not be fixed, then we are interested in this as well, but more likely > than not the fix will be rolled back and rescheduled for 2.0.10. > Naturally the importance of the issue has bearing in how this will be > handled. > > > > * If we can receive a sample project or IT[2] showing the issue, > then > it increases the likelihood of a quick fix and turnaround of the RC > exponentially, both for regressions and for "not fixed" issues in > 2.0.9 > > > > * Please report any regressions found between earlier versions of > 2.0.x and 2.0.9 as they will be prioritized for 2.0.10 along with > anything rolled back / not fixed from 2.0.9 > > > > * We will continue to iterate through this process until we feel > that > the release is ready to go. User list input will have a large > factor in > making this decision. That said, the quality of the 2.0.9 release will > depend on the level of involvement from the entire community to test, > reproduce and report issues identified. > > > > * Please file a Jira[3] for anything you find, and then reply to the > RC thread with the details and issue number so that others may see and > reduce duplicate reports. We will be watching Jira closely for reports > with 2.0.9 in the affected version. > > > > * Once a release is ready, we will rebuild and restage the code from > the most recent RC for a formal vote. This will produce the official > "2.0.9" release. > > > > The list of issues fixed for this release can be found here: > > http://jira.codehaus.org/secure/ReleaseNote.jspa? > version=13801&styleName > =Html&projectId=10500&Create=Create > > > > Some notable changes are: > > * Plugin versions are locked in the superpom. (MNG-3395) You can see > the locked versions here: > > http://svn.apache.org/repos/asf/maven/components/branches/ > maven-2.0.x/ma > ven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml > > > > * In most cases they are locked to the currently available plugin to > avoid suddenly downgrading users that haven't locked their own > versions > (still the best practice). > > > > * Webdav is included in the core, meaning you can deploy:deploy-file > without a pom to include the extension (if you use webdav obviously) > (MNG-2664) > > > > * New syntax for mirror definitions. Details here: MNG-3461 > > > > * Introduction of Import scope: (MNG-3220) > > http://maven.apache.org/guides/introduction/introduction-to- > dependency-m > echanism.html#Importing_Dependencies > > > > > > The binaries for this RC can be found here: > > http://people.apache.org/~brianf/staging-repository/org/apache/ > maven/apa > che-maven/ > > (naturally take the highest RC number deployed as it will change > when we > iterate) > > > > [1] Previous RC threads: > > > http://www.nabble.com/-Pre-Vote--release-maven-2.0.9- > td16124759s177.html > > http://www.nabble.com/-pre-vote-take-3--2.0.9-RC3-td16314473s177.html > > http://www.nabble.com/-2.0.9-RC4--td16344067s177.html > > http://www.nabble.com/-2.0.9-RC5--td16365465s177.html#a16365465 > > > > [2] Creating a Core IT: > > http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration > +Test > > > > [3] http://jira.codehaus.org/browse/MNG > > > > > > Thanks, > > The Maven Team > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john rss: http://feeds.feedburner.com/ejlife/john |
|
|
RE: [2.0.9 RC6] Release Candidate testing
by Chris Schmidt-3
::
Rate this Message:
I don't see any issue with my build either.
Thanks, Chris Schmidt -----Original Message----- From: Brian E. Fox [mailto:brianf@...] Sent: Tuesday, April 01, 2008 4:35 PM To: Maven Users List Subject: [2.0.9 RC6] Release Candidate testing I didn't get much response yesterday and we respun a new RC (RC6) so I'm resending the original mail. If nothing turns up within 3 days, then we will restage and vote for a release. Thanks, Brian --------------------------------------- In an attempt to raise quality and reduce/eliminate regressions in the core releases, we are experimenting with a new release process. The old process had a few informal staged builds followed by one or more official staged builds that where voted on. Clearly this didn't attract enough testing prior to the official release to identify regressions or other major issues. The new process we are using for the 2.0.9 release is to cut actual release candidate (RCx) releases. These are released with the normal release process so it generates a tag, but do not get sync'd to central. We have gone through several RCs[1] as we tested on the dev@ list. The next step is to open it up to the user list for fix validation and regression identification. This is really the first time we've followed such a process so we'll have to see how it pans out. Here are the "operating parameters" for this test: * The goal of the RCs are to stabilize the release and any changes at this point naturally risks further regressions. Therefore, the list of fixes for 2.0.9 is locked. We will not be including any more fixes at this point unless it meets the requirements laid out below. This means please don't reply with "could you just include xyz". * The issues we are looking to identify and fix are those where it can be shown to work with 2.0.8, but not with 2.0.9-RCxxx. These issues we will almost certainly fix. Our goal is to fix ALL regressions identified between 2.0.8 and 2.0.9, but naturally we need to weigh the severity of the issue along with the exposure against the complexity and risk of further regressions by fixing it. * If any of the issues that are marked as fixed for 2.0.9 are found to not be fixed, then we are interested in this as well, but more likely than not the fix will be rolled back and rescheduled for 2.0.10. Naturally the importance of the issue has bearing in how this will be handled. * If we can receive a sample project or IT[2] showing the issue, then it increases the likelihood of a quick fix and turnaround of the RC exponentially, both for regressions and for "not fixed" issues in 2.0.9 * Please report any regressions found between earlier versions of 2.0.x and 2.0.9 as they will be prioritized for 2.0.10 along with anything rolled back / not fixed from 2.0.9 * We will continue to iterate through this process until we feel that the release is ready to go. User list input will have a large factor in making this decision. That said, the quality of the 2.0.9 release will depend on the level of involvement from the entire community to test, reproduce and report issues identified. * Please file a Jira[3] for anything you find, and then reply to the RC thread with the details and issue number so that others may see and reduce duplicate reports. We will be watching Jira closely for reports with 2.0.9 in the affected version. * Once a release is ready, we will rebuild and restage the code from the most recent RC for a formal vote. This will produce the official "2.0.9" release. The list of issues fixed for this release can be found here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13801&styleName =Html&projectId=10500&Create=Create Some notable changes are: * Plugin versions are locked in the superpom. (MNG-3395) You can see the locked versions here: http://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/ma ven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml * In most cases they are locked to the currently available plugin to avoid suddenly downgrading users that haven't locked their own versions (still the best practice). * Webdav is included in the core, meaning you can deploy:deploy-file without a pom to include the extension (if you use webdav obviously) (MNG-2664) * New syntax for mirror definitions. Details here: MNG-3461 * Introduction of Import scope: (MNG-3220) http://maven.apache.org/guides/introduction/introduction-to-dependency-m echanism.html#Importing_Dependencies The binaries for this RC can be found here: http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/ (naturally take the highest RC number deployed as it will change when we iterate) [1] Previous RC threads: http://www.nabble.com/-Pre-Vote--release-maven-2.0.9-td16124759s177.html http://www.nabble.com/-pre-vote-take-3--2.0.9-RC3-td16314473s177.html http://www.nabble.com/-2.0.9-RC4--td16344067s177.html http://www.nabble.com/-2.0.9-RC5--td16365465s177.html#a16365465 [2] Creating a Core IT: http://docs.codehaus.org/display/MAVEN/Creating+a+Maven+Integration+Test [3] http://jira.codehaus.org/browse/MNG Thanks, The Maven Team The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and destroy all copies of the original message. Thank you --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
|
|
|
[2.0.9 RC7] Release Candidate testing
by Brian E Fox
::
Rate this Message:
Thank you everyone for the testing and confirmatory responses so far. It
helps to gauge the progress. There was one regression identified in 2.0.9 RC6: (MNG-3495: NPE at org.apache.maven.wagon.repository.Repository.hashCode). This has been fixed and RC7 posted. Various users have identified some issues with the site plugin that seem to occur when switching to 2.0.9. This can happen because we started locking down versions in 2.0.9. This is so if you haven't specified a version in your poms, it won't change on you going forward. This means that you will get upgraded to the latest site plugin (2.0-beta-6) just like you would if you did mvn -U on your build. If you have trouble with site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5 in your pom (we recommend locking your versions anyway). This is preferable to locking 2.0.9 to beta-5 for everyone and potentially forcing some people's versions backwards. In the future, only the most stable versions will be locked in the super pom and usually this will not be the most recent release. Since 2.0.9 was the first time we did this, we had to go with the current versions as the baseline. RC7 is available for download here: http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/ Thank you for your assistance in testing the RCs. --Brian --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
[2.0.9 RC7] Release Candidate testing
by Brian E Fox
::
Rate this Message:
Thank you everyone for the testing and confirmatory responses so far. It
helps to gauge the progress. There was one regression identified in 2.0.9 RC6: (MNG-3495: NPE at org.apache.maven.wagon.repository.Repository.hashCode). This has been fixed and RC7 posted. Various users have identified some issues with the site plugin that seem to occur when switching to 2.0.9. This can happen because we started locking down versions in 2.0.9. This is so if you haven't specified a version in your poms, it won't change on you going forward. This means that you will get upgraded to the latest site plugin (2.0-beta-6) just like you would if you did mvn -U on your build. If you have trouble with site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5 in your pom (we recommend locking your versions anyway). This is preferable to locking 2.0.9 to beta-5 for everyone and potentially forcing some people's versions backwards. In the future, only the most stable versions will be locked in the super pom and usually this will not be the most recent release. Since 2.0.9 was the first time we did this, we had to go with the current versions as the baseline. RC7 is available for download here: http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/ Thank you for your assistance in testing the RCs. --Brian --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: [2.0.9 RC7] Release Candidate testing
by Kaizer H. Sogiawala
::
Rate this Message:
I am getting a strange behavior with apache-maven-2.0.9-RC* (all RC)
builds. Here is what I see- --- SNIP --- + Error stacktraces are turned on. Maven version: 2.0.9-RC7 Java version: 1.5.0_12 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\blip\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\Program Files\maven\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... : : *blip blip* : [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] String index out of range: -1 [INFO] ------------------------------------------------------------------------ [DEBUG] Trace java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1768) at java.lang.String.substring(String.java:1735) at org.apache.maven.project.path.DefaultPathTranslator.stripBasedirToken(DefaultPathTranslator.java:101) at org.apache.maven.project.path.DefaultPathTranslator.alignToBaseDirectory(DefaultPathTranslator.java:82) at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:992) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:867) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:495) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) 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 Apr 02 21:40:25 PDT 2008 [INFO] Final Memory: 1M/2M [INFO] ------------------------------------------------------------------------ --- SNIP --- This project is working fine with a 2.0.9-SNAPSHOT build with following date/time stamp- #Generated by Maven #Thu Feb 21 21:53:42 PST 2008 version=2.0.9-SNAPSHOT groupId=org.apache.maven artifactId=maven-core -- Our build system uses multiple plugins developed inhouse with packaging type and forked lifecycle. On Wed, Apr 2, 2008 at 2:52 PM, Brian E. Fox <brianf@...> wrote: > Thank you everyone for the testing and confirmatory responses so far. It > helps to gauge the progress. There was one regression identified in > 2.0.9 RC6: (MNG-3495: NPE at > org.apache.maven.wagon.repository.Repository.hashCode). This has been > fixed and RC7 posted. > > Various users have identified some issues with the site plugin that seem > to occur when switching to 2.0.9. This can happen because we started > locking down versions in 2.0.9. This is so if you haven't specified a > version in your poms, it won't change on you going forward. This means > that you will get upgraded to the latest site plugin (2.0-beta-6) just > like you would if you did mvn -U on your build. If you have trouble with > site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5 in > your pom (we recommend locking your versions anyway). This is preferable > to locking 2.0.9 to beta-5 for everyone and potentially forcing some > people's versions backwards. > > In the future, only the most stable versions will be locked in the super > pom and usually this will not be the most recent release. Since 2.0.9 > was the first time we did this, we had to go with the current versions > as the baseline. > > RC7 is available for download here: > > http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa > che-maven/ > > > Thank you for your assistance in testing the RCs. > > --Brian > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- + Kaizer H. Sogiawala + --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
RE: [2.0.9 RC7] Release Candidate testing
by Brian E Fox
::
Rate this Message:
Do you have a way to reproduce this? The DefaultPathTranslator class
hasn't changed since 2.0.6 so it must be a higher level change we're looking for. -----Original Message----- From: Kaizer H. Sogiawala [mailto:kaizers@...] Sent: Thursday, April 03, 2008 12:49 AM To: Maven Users List Subject: Re: [2.0.9 RC7] Release Candidate testing I am getting a strange behavior with apache-maven-2.0.9-RC* (all RC) builds. Here is what I see- --- SNIP --- + Error stacktraces are turned on. Maven version: 2.0.9-RC7 Java version: 1.5.0_12 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\blip\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\Program Files\maven\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... : : *blip blip* : [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] String index out of range: -1 [INFO] ------------------------------------------------------------------------ [DEBUG] Trace java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1768) at java.lang.String.substring(String.java:1735) at org.apache.maven.project.path.DefaultPathTranslator.stripBasedirToken(De faultPathTranslator.java:101) at org.apache.maven.project.path.DefaultPathTranslator.alignToBaseDirectory (DefaultPathTranslator.java:82) at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic( DefaultMavenProjectBuilder.java:992) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul tMavenProjectBuilder.java:867) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI nternal(DefaultMavenProjectBuilder.java:495) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr ojectBuilder.java:198) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) 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.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.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 Apr 02 21:40:25 PDT 2008 [INFO] Final Memory: 1M/2M [INFO] ------------------------------------------------------------------------ --- SNIP --- This project is working fine with a 2.0.9-SNAPSHOT build with following date/time stamp- #Generated by Maven #Thu Feb 21 21:53:42 PST 2008 version=2.0.9-SNAPSHOT groupId=org.apache.maven artifactId=maven-core -- Our build system uses multiple plugins developed inhouse with packaging type and forked lifecycle. On Wed, Apr 2, 2008 at 2:52 PM, Brian E. Fox <brianf@...> wrote: > Thank you everyone for the testing and confirmatory responses so far. It > helps to gauge the progress. There was one regression identified in > 2.0.9 RC6: (MNG-3495: NPE at > org.apache.maven.wagon.repository.Repository.hashCode). This has been > fixed and RC7 posted. > > Various users have identified some issues with the site plugin that seem > to occur when switching to 2.0.9. This can happen because we started > locking down versions in 2.0.9. This is so if you haven't specified a > version in your poms, it won't change on you going forward. This means > that you will get upgraded to the latest site plugin (2.0-beta-6) just > like you would if you did mvn -U on your build. If you have trouble with > site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5 in > your pom (we recommend locking your versions anyway). This is preferable > to locking 2.0.9 to beta-5 for everyone and potentially forcing some > people's versions backwards. > > In the future, only the most stable versions will be locked in the super > pom and usually this will not be the most recent release. Since 2.0.9 > was the first time we did this, we had to go with the current versions > as the baseline. > > RC7 is available for download here: > > http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa > che-maven/ > > > Thank you for your assistance in testing the RCs. > > --Brian > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- + Kaizer H. Sogiawala + --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: [2.0.9 RC7] Release Candidate testing
by Brett Porter
::
Rate this Message:
-1 could be empty string, and there were some hacks in the project
builder that set expressions to that. I know that the path translator was effected by interpolation changes, even though indirectly, because the values got interpolated after instead of before. I'd look at those changes - though a POM that reproduces it is probably necessary to do so. - Brett On 04/04/2008, Brian E. Fox <brianf@...> wrote: > Do you have a way to reproduce this? The DefaultPathTranslator class > hasn't changed since 2.0.6 so it must be a higher level change we're > looking for. > > > -----Original Message----- > From: Kaizer H. Sogiawala [mailto:kaizers@...] > Sent: Thursday, April 03, 2008 12:49 AM > To: Maven Users List > > Subject: Re: [2.0.9 RC7] Release Candidate testing > > I am getting a strange behavior with apache-maven-2.0.9-RC* (all RC) > builds. Here is what I see- > > --- SNIP --- > + Error stacktraces are turned on. > Maven version: 2.0.9-RC7 > Java version: 1.5.0_12 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents > and Settings\blip\.m2\plugin-registry.xml' > [DEBUG] Building Maven global-level plugin registry from: 'C:\Program > Files\maven\bin\..\conf\plugin-registry.xml' > [INFO] Scanning for projects... > : > : *blip blip* > : > [INFO] > ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] String index out of range: -1 > [INFO] > ------------------------------------------------------------------------ > [DEBUG] Trace > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > at java.lang.String.substring(String.java:1768) > at java.lang.String.substring(String.java:1735) > at > org.apache.maven.project.path.DefaultPathTranslator.stripBasedirToken(De > faultPathTranslator.java:101) > at > org.apache.maven.project.path.DefaultPathTranslator.alignToBaseDirectory > (DefaultPathTranslator.java:82) > at > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic( > DefaultMavenProjectBuilder.java:992) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul > tMavenProjectBuilder.java:867) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI > nternal(DefaultMavenProjectBuilder.java:495) > at > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr > ojectBuilder.java:198) > at > org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) > at > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) > at > org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) > at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > 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.jav > a:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > Impl.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 Apr 02 21:40:25 PDT 2008 > [INFO] Final Memory: 1M/2M > [INFO] > ------------------------------------------------------------------------ > > --- SNIP --- > > This project is working fine with a 2.0.9-SNAPSHOT build with > following date/time stamp- > > #Generated by Maven > #Thu Feb 21 21:53:42 PST 2008 > version=2.0.9-SNAPSHOT > groupId=org.apache.maven > artifactId=maven-core > > -- > > Our build system uses multiple plugins developed inhouse with > packaging type and forked lifecycle. > > > On Wed, Apr 2, 2008 at 2:52 PM, Brian E. Fox <brianf@...> > wrote: > > Thank you everyone for the testing and confirmatory responses so far. > It > > helps to gauge the progress. There was one regression identified in > > 2.0.9 RC6: (MNG-3495: NPE at > > org.apache.maven.wagon.repository.Repository.hashCode). This has been > > fixed and RC7 posted. > > > > Various users have identified some issues with the site plugin that > seem > > to occur when switching to 2.0.9. This can happen because we started > > locking down versions in 2.0.9. This is so if you haven't specified a > > version in your poms, it won't change on you going forward. This > means > > that you will get upgraded to the latest site plugin (2.0-beta-6) > just > > like you would if you did mvn -U on your build. If you have trouble > with > > site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5 > in > > your pom (we recommend locking your versions anyway). This is > preferable > > to locking 2.0.9 to beta-5 for everyone and potentially forcing some > > people's versions backwards. > > > > In the future, only the most stable versions will be locked in the > super > > pom and usually this will not be the most recent release. Since 2.0.9 > > was the first time we did this, we had to go with the current > versions > > as the baseline. > > > > RC7 is available for download here: > > > > > http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa > > che-maven/ > > > > > > Thank you for your assistance in testing the RCs. > > > > --Brian > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > For additional commands, e-mail: users-help@... > > > > > > > > -- > + Kaizer H. Sogiawala + > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- Brett Porter Blog: http://blogs.exist.com/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: [2.0.9 RC7] Release Candidate testing
by John Casey-5
::
Rate this Message:
FWIW, using:
<build> <directory>${basedir}</directory> </build> will express this error. See http://jira.codehaus.org/browse/MNG-3498 I have the fix, just need to get it cleaned up and committed. -john On Apr 3, 2008, at 11:23 AM, Brett Porter wrote: > -1 could be empty string, and there were some hacks in the project > builder that set expressions to that. I know that the path translator > was effected by interpolation changes, even though indirectly, because > the values got interpolated after instead of before. > > I'd look at those changes - though a POM that reproduces it is > probably necessary to do so. > > - Brett > > On 04/04/2008, Brian E. Fox <brianf@...> wrote: >> Do you have a way to reproduce this? The DefaultPathTranslator class >> hasn't changed since 2.0.6 so it must be a higher level change we're >> looking for. >> >> >> -----Original Message----- >> From: Kaizer H. Sogiawala [mailto:kaizers@...] >> Sent: Thursday, April 03, 2008 12:49 AM >> To: Maven Users List >> >> Subject: Re: [2.0.9 RC7] Release Candidate testing >> >> I am getting a strange behavior with apache-maven-2.0.9-RC* (all RC) >> builds. Here is what I see- >> >> --- SNIP --- >> + Error stacktraces are turned on. >> Maven version: 2.0.9-RC7 >> Java version: 1.5.0_12 >> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >> [DEBUG] Building Maven user-level plugin registry from: 'C: >> \Documents >> and Settings\blip\.m2\plugin-registry.xml' >> [DEBUG] Building Maven global-level plugin registry from: 'C: >> \Program >> Files\maven\bin\..\conf\plugin-registry.xml' >> [INFO] Scanning for projects... >> : >> : *blip blip* >> : >> [INFO] >> >> --------------------------------------------------------------------- >> --- >> [ERROR] FATAL ERROR >> [INFO] >> >> --------------------------------------------------------------------- >> --- >> [INFO] String index out of range: -1 >> [INFO] >> >> --------------------------------------------------------------------- >> --- >> [DEBUG] Trace >> java.lang.StringIndexOutOfBoundsException: String index out of >> range: -1 >> at java.lang.String.substring(String.java:1768) >> at java.lang.String.substring(String.java:1735) >> at >> >> org.apache.maven.project.path.DefaultPathTranslator.stripBasedirToken >> (De >> faultPathTranslator.java:101) >> at >> >> org.apache.maven.project.path.DefaultPathTranslator.alignToBaseDirect >> ory >> (DefaultPathTranslator.java:82) >> at >> >> org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLog >> ic( >> DefaultMavenProjectBuilder.java:992) >> at >> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal >> (Defaul >> tMavenProjectBuilder.java:867) >> at >> >> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi >> leI >> nternal(DefaultMavenProjectBuilder.java:495) >> at >> org.apache.maven.project.DefaultMavenProjectBuilder.build >> (DefaultMavenPr >> ojectBuilder.java:198) >> at >> org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) >> at >> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) >> at >> org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) >> at >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) >> 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.jav >> a:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke >> (DelegatingMethodAccessor >> Impl.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 Apr 02 21:40:25 PDT 2008 >> [INFO] Final Memory: 1M/2M >> [INFO] >> >> --------------------------------------------------------------------- >> --- >> >> --- SNIP --- >> >> This project is working fine with a 2.0.9-SNAPSHOT build with >> following date/time stamp- >> >> #Generated by Maven >> #Thu Feb 21 21:53:42 PST 2008 >> version=2.0.9-SNAPSHOT >> groupId=org.apache.maven >> artifactId=maven-core >> >> -- >> >> Our build system uses multiple plugins developed inhouse with >> packaging type and forked lifecycle. >> >> >> On Wed, Apr 2, 2008 at 2:52 PM, Brian E. Fox >> <brianf@...> >> wrote: >>> Thank you everyone for the testing and confirmatory responses so >>> far. >> It >>> helps to gauge the progress. There was one regression identified in >>> 2.0.9 RC6: (MNG-3495: NPE at >>> org.apache.maven.wagon.repository.Repository.hashCode). This has >>> been >>> fixed and RC7 posted. >>> >>> Various users have identified some issues with the site plugin that >> seem >>> to occur when switching to 2.0.9. This can happen because we >>> started >>> locking down versions in 2.0.9. This is so if you haven't >>> specified a >>> version in your poms, it won't change on you going forward. This >> means >>> that you will get upgraded to the latest site plugin (2.0-beta-6) >> just >>> like you would if you did mvn -U on your build. If you have trouble >> with >>> site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5 >> in >>> your pom (we recommend locking your versions anyway). This is >> preferable >>> to locking 2.0.9 to beta-5 for everyone and potentially forcing >>> some >>> people's versions backwards. >>> >>> In the future, only the most stable versions will be locked in the >> super >>> pom and usually this will not be the most recent release. Since >>> 2.0.9 >>> was the first time we did this, we had to go with the current >> versions >>> as the baseline. >>> >>> RC7 is available for download here: >>> >>> >> http://people.apache.org/~brianf/staging-repository/org/apache/ >> maven/apa >>> che-maven/ >>> >>> >>> Thank you for your assistance in testing the RCs. >>> >>> --Brian >>> >>> >>> -------------------------------------------------------------------- >>> - >>> >>> >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >>> >> >> >> >> -- >> + Kaizer H. Sogiawala + >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> > > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john rss: http://feeds.feedburner.com/ejlife/john |
|
|
Re: [2.0.9 RC7] Release Candidate testing
by Kaizer H. Sogiawala
::
Rate this Message:
I debugged through the source and can confirm
"<directory>${basedir}</directory>" is the issue. On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jdcasey@...> wrote: > FWIW, using: > > <build> > <directory>${basedir}</directory> > </build> > > will express this error. See http://jira.codehaus.org/browse/MNG-3498 > > I have the fix, just need to get it cleaned up and committed. > > -john > > > > On Apr 3, 2008, at 11:23 AM, Brett Porter wrote: > > > > -1 could be empty string, and there were some hacks in the project > > builder that set expressions to that. I know that the path translator > > was effected by interpolation changes, even though indirectly, because > > the values got interpolated after instead of before. > > > > I'd look at those changes - though a POM that reproduces it is > > probably necessary to do so. > > > > - Brett > > > > On 04/04/2008, Brian E. Fox <brianf@...> wrote: > > > > > Do you have a way to reproduce this? The DefaultPathTranslator class > > > hasn't changed since 2.0.6 so it must be a higher level change we're > > > looking for. > > > > > > > > > -----Original Message----- > > > From: Kaizer H. Sogiawala [mailto:kaizers@...] > > > Sent: Thursday, April 03, 2008 12:49 AM > > > To: Maven Users List > > > > > > Subject: Re: [2.0.9 RC7] Release Candidate testing > > > > > > I am getting a strange behavior with apache-maven-2.0.9-RC* (all RC) > > > builds. Here is what I see- > > > > > > --- SNIP --- > > > + Error stacktraces are turned on. > > > Maven version: 2.0.9-RC7 > > > Java version: 1.5.0_12 > > > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > > > [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents > > > and Settings\blip\.m2\plugin-registry.xml' > > > [DEBUG] Building Maven global-level plugin registry from: 'C:\Program > > > Files\maven\bin\..\conf\plugin-registry.xml' > > > [INFO] Scanning for projects... > > > : > > > : *blip blip* > > > : > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [ERROR] FATAL ERROR > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [INFO] String index out of range: -1 > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [DEBUG] Trace > > > java.lang.StringIndexOutOfBoundsException: String index out of range: > -1 > > > at java.lang.String.substring(String.java:1768) > > > at java.lang.String.substring(String.java:1735) > > > at > > > > org.apache.maven.project.path.DefaultPathTranslator.stripBasedirToken(De > > > faultPathTranslator.java:101) > > > at > > > > org.apache.maven.project.path.DefaultPathTranslator.alignToBaseDirectory > > > (DefaultPathTranslator.java:82) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic( > > > DefaultMavenProjectBuilder.java:992) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul > > > tMavenProjectBuilder.java:867) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI > > > nternal(DefaultMavenProjectBuilder.java:495) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr > > > ojectBuilder.java:198) > > > at > > > org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) > > > at > > > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) > > > at > > > org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) > > > at > > > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > > > 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.jav > > > a:39) > > > at > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > > > Impl.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 Apr 02 21:40:25 PDT 2008 > > > [INFO] Final Memory: 1M/2M > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > > > --- SNIP --- > > > > > > This project is working fine with a 2.0.9-SNAPSHOT build with > > > following date/time stamp- > > > > > > #Generated by Maven > > > #Thu Feb 21 21:53:42 PST 2008 > > > version=2.0.9-SNAPSHOT > > > groupId=org.apache.maven > > > artifactId=maven-core > > > > > > -- > > > > > > Our build system uses multiple plugins developed inhouse with > > > packaging type and forked lifecycle. > > > > > > > > > On Wed, Apr 2, 2008 at 2:52 PM, Brian E. Fox <brianf@...> > > > wrote: > > > > > > > Thank you everyone for the testing and confirmatory responses so far. > > > > > > > It > > > > > > > helps to gauge the progress. There was one regression identified in > > > > 2.0.9 RC6: (MNG-3495: NPE at > > > > org.apache.maven.wagon.repository.Repository.hashCode). This has been > > > > fixed and RC7 posted. > > > > > > > > Various users have identified some issues with the site plugin that > > > > > > > seem > > > > > > > to occur when switching to 2.0.9. This can happen because we started > > > > locking down versions in 2.0.9. This is so if you haven't specified a > > > > version in your poms, it won't change on you going forward. This > > > > > > > means > > > > > > > that you will get upgraded to the latest site plugin (2.0-beta-6) > > > > > > > just > > > > > > > like you would if you did mvn -U on your build. If you have trouble > > > > > > > with > > > > > > > site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5 > > > > > > > in > > > > > > > your pom (we recommend locking your versions anyway). This is > > > > > > > preferable > > > > > > > to locking 2.0.9 to beta-5 for everyone and potentially forcing some > > > > people's versions backwards. > > > > > > > > In the future, only the most stable versions will be locked in the > > > > > > > super > > > > > > > pom and usually this will not be the most recent release. Since 2.0.9 > > > > was the first time we did this, we had to go with the current > > > > > > > versions > > > > > > > as the baseline. > > > > > > > > RC7 is available for download here: > > > > > > > > > > > > > > > > http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa > > > > > > > che-maven/ > > > > > > > > > > > > Thank you for your assistance in testing the RCs. > > > > > > > > --Brian > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > > > For additional commands, e-mail: users-help@... > > > > > > > > > > > > > > > > > > > > > > > > -- > > > + Kaizer H. Sogiawala + > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscribe@... > > > For additional commands, e-mail: users-help@... > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscribe@... > > > For additional commands, e-mail: users-help@... > > > > > > > > > > > > > > > -- > > Brett Porter > > Blog: http://blogs.exist.com/bporter/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscribe@... > > For additional commands, e-mail: users-help@... > > > > > > > --- > John Casey > Committer and PMC Member, Apache Maven > mail: jdcasey at commonjava dot org > blog: http://www.ejlife.net/blogs/john > rss: http://feeds.feedburner.com/ejlife/john > > > -- + Kaizer H. Sogiawala + --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
RE: [2.0.9 RC7] Release Candidate testing
by Brian E Fox
::
Rate this Message:
I'm about to build and release RC8 with this fix.
-----Original Message----- From: Kaizer H. Sogiawala [mailto:kaizers@...] Sent: Thursday, April 03, 2008 2:51 PM To: Maven Users List Subject: Re: [2.0.9 RC7] Release Candidate testing I debugged through the source and can confirm "<directory>${basedir}</directory>" is the issue. On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jdcasey@...> wrote: > FWIW, using: > > <build> > <directory>${basedir}</directory> > </build> > > will express this error. See http://jira.codehaus.org/browse/MNG-3498 > > I have the fix, just need to get it cleaned up and committed. > > -john > > > > On Apr 3, 2008, at 11:23 AM, Brett Porter wrote: > > > > -1 could be empty string, and there were some hacks in the project > > builder that set expressions to that. I know that the path > > was effected by interpolation changes, even though indirectly, because > > the values got interpolated after instead of before. > > > > I'd look at those changes - though a POM that reproduces it is > > probably necessary to do so. > > > > - Brett > > > > On 04/04/2008, Brian E. Fox <brianf@...> wrote: > > > > > Do you have a way to reproduce this? The DefaultPathTranslator > > > hasn't changed since 2.0.6 so it must be a higher level change we're > > > looking for. > > > > > > > > > -----Original Message----- > > > From: Kaizer H. Sogiawala [mailto:kaizers@...] > > > Sent: Thursday, April 03, 2008 12:49 AM > > > To: Maven Users List > > > > > > Subject: Re: [2.0.9 RC7] Release Candidate testing > > > > > > I am getting a strange behavior with apache-maven-2.0.9-RC* (all > > > builds. Here is what I see- > > > > > > --- SNIP --- > > > + Error stacktraces are turned on. > > > Maven version: 2.0.9-RC7 > > > Java version: 1.5.0_12 > > > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > > > [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents > > > and Settings\blip\.m2\plugin-registry.xml' > > > [DEBUG] Building Maven global-level plugin registry from: 'C:\Program > > > Files\maven\bin\..\conf\plugin-registry.xml' > > > [INFO] Scanning for projects... > > > : > > > : *blip blip* > > > : > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [ERROR] FATAL ERROR > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [INFO] String index out of range: -1 > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [DEBUG] Trace > > > java.lang.StringIndexOutOfBoundsException: String index out of range: > -1 > > > at java.lang.String.substring(String.java:1768) > > > at java.lang.String.substring(String.java:1735) > > > at > > > > org.apache.maven.project.path.DefaultPathTranslator.stripBasedirToken(De > > > faultPathTranslator.java:101) > > > at > > > > org.apache.maven.project.path.DefaultPathTranslator.alignToBaseDirectory > > > (DefaultPathTranslator.java:82) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic( > > > DefaultMavenProjectBuilder.java:992) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul > > > tMavenProjectBuilder.java:867) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI > > > nternal(DefaultMavenProjectBuilder.java:495) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr > > > ojectBuilder.java:198) > > > at > > > org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) > > > at > > > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) > > > at > > > org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) > > > at > > > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > > > 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.jav > > > a:39) > > > at > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > > > Impl.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 Apr 02 21:40:25 PDT 2008 > > > [INFO] Final Memory: 1M/2M > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > > > --- SNIP --- > > > > > > This project is working fine with a 2.0.9-SNAPSHOT build with > > > following date/time stamp- > > > > > > #Generated by Maven > > > #Thu Feb 21 21:53:42 PST 2008 > > > version=2.0.9-SNAPSHOT > > > groupId=org.apache.maven > > > artifactId=maven-core > > > > > > -- > > > > > > Our build system uses multiple plugins developed inhouse with > > > packaging type and forked lifecycle. > > > > > > > > > On Wed, Apr 2, 2008 at 2:52 PM, Brian E. Fox > > > wrote: > > > > > > > Thank you everyone for the testing and confirmatory responses so far. > > > > > > > It > > > > > > > helps to gauge the progress. There was one regression identified in > > > > 2.0.9 RC6: (MNG-3495: NPE at > > > > org.apache.maven.wagon.repository.Repository.hashCode). This has been > > > > fixed and RC7 posted. > > > > > > > > Various users have identified some issues with the site plugin that > > > > > > > seem > > > > > > > to occur when switching to 2.0.9. This can happen because we started > > > > locking down versions in 2.0.9. This is so if you haven't specified a > > > > version in your poms, it won't change on you going forward. This > > > > > > > means > > > > > > > that you will get upgraded to the latest site plugin (2.0-beta-6) > > > > > > > just > > > > > > > like you would if you did mvn -U on your build. If you have trouble > > > > > > > with > > > > > > > site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5 > > > > > > > in > > > > > > > your pom (we recommend locking your versions anyway). This is > > > > > > > preferable > > > > > > > to locking 2.0.9 to beta-5 for everyone and potentially forcing some > > > > people's versions backwards. > > > > > > > > In the future, only the most stable versions will be locked in the > > > > > > > super > > > > > > > pom and usually this will not be the most recent release. Since 2.0.9 > > > > was the first time we did this, we had to go with the current > > > > > > > versions > > > > > > > as the baseline. > > > > > > > > RC7 is available for download here: > > > > > > > > > > > > > > > > > > > > > > > che-maven/ > > > > > > > > > > > > Thank you for your assistance in testing the RCs. > > > > > > > > --Brian > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > > > For additional commands, e-mail: users-help@... > > > > > > > > > > > > > > > > > > > > > > > > -- > > > + Kaizer H. Sogiawala + > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > > For additional commands, e-mail: users-help@... > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscribe@... > > > For additional commands, e-mail: users-help@... > > > > > > > > > > > > > > > -- > > Brett Porter > > Blog: http://blogs.exist.com/bporter/ > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > For additional commands, e-mail: users-help@... > > > > > > > --- > John Casey > Committer and PMC Member, Apache Maven > mail: jdcasey at commonjava dot org > blog: http://www.ejlife.net/blogs/john > rss: http://feeds.feedburner.com/ejlife/john > > > -- + Kaizer H. Sogiawala + --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: [2.0.9 RC7] Release Candidate testing
by Haroon Rafique
::
Rate this Message:
On Yesterday at 5:52pm, BEF=>Brian E. Fox <brianf@...> wrote:
BEF> Thank you everyone for the testing and confirmatory responses so far. BEF> It helps to gauge the progress. There was one regression identified BEF> in 2.0.9 RC6: (MNG-3495: NPE at BEF> org.apache.maven.wagon.repository.Repository.hashCode). This has been BEF> fixed and RC7 posted. BEF> BEF> [..snip..] +1 No problems with my projects Thanks, -- Haroon Rafique <haroon.rafique@...> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
[2.0.9 RC8] Release Candidate testing
by Brian E Fox
::
Rate this Message:
RC8 posted to solve this regression.
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/ -----Original Message----- From: Kaizer H. Sogiawala [mailto:kaizers@...] Sent: Thursday, April 03, 2008 2:51 PM To: Maven Users List Subject: Re: [2.0.9 RC7] Release Candidate testing I debugged through the source and can confirm "<directory>${basedir}</directory>" is the issue. On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jdcasey@...> wrote: > FWIW, using: > > <build> > <directory>${basedir}</directory> > </build> > > will express this error. See http://jira.codehaus.org/browse/MNG-3498 > > I have the fix, just need to get it cleaned up and committed. > > -john > > > > On Apr 3, 2008, at 11:23 AM, Brett Porter wrote: > > > > -1 could be empty string, and there were some hacks in the project > > builder that set expressions to that. I know that the path > > was effected by interpolation changes, even though indirectly, because > > the values got interpolated after instead of before. > > > > I'd look at those changes - though a POM that reproduces it is > > probably necessary to do so. > > > > - Brett > > > > On 04/04/2008, Brian E. Fox <brianf@...> wrote: > > > > > Do you have a way to reproduce this? The DefaultPathTranslator > > > hasn't changed since 2.0.6 so it must be a higher level change we're > > > looking for. > > > > > > > > > -----Original Message----- > > > From: Kaizer H. Sogiawala [mailto:kaizers@...] > > > Sent: Thursday, April 03, 2008 12:49 AM > > > To: Maven Users List > > > > > > Subject: Re: [2.0.9 RC7] Release Candidate testing > > > > > > I am getting a strange behavior with apache-maven-2.0.9-RC* (all > > > builds. Here is what I see- > > > > > > --- SNIP --- > > > + Error stacktraces are turned on. > > > Maven version: 2.0.9-RC7 > > > Java version: 1.5.0_12 > > > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > > > [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents > > > and Settings\blip\.m2\plugin-registry.xml' > > > [DEBUG] Building Maven global-level plugin registry from: 'C:\Program > > > Files\maven\bin\..\conf\plugin-registry.xml' > > > [INFO] Scanning for projects... > > > : > > > : *blip blip* > > > : > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [ERROR] FATAL ERROR > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [INFO] String index out of range: -1 > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [DEBUG] Trace > > > java.lang.StringIndexOutOfBoundsException: String index out of range: > -1 > > > at java.lang.String.substring(String.java:1768) > > > at java.lang.String.substring(String.java:1735) > > > at > > > > org.apache.maven.project.path.DefaultPathTranslator.stripBasedirToken(De > > > faultPathTranslator.java:101) > > > at > > > > org.apache.maven.project.path.DefaultPathTranslator.alignToBaseDirectory > > > (DefaultPathTranslator.java:82) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic( > > > DefaultMavenProjectBuilder.java:992) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul > > > tMavenProjectBuilder.java:867) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI > > > nternal(DefaultMavenProjectBuilder.java:495) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr > > > ojectBuilder.java:198) > > > at > > > org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) > > > at > > > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) > > > at > > > org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) > > > at > > > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > > > 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.jav > > > a:39) > > > at > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > > > Impl.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 Apr 02 21:40:25 PDT 2008 > > > [INFO] Final Memory: 1M/2M > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > > > --- SNIP --- > > > > > > This project is working fine with a 2.0.9-SNAPSHOT build with > > > following date/time stamp- > > > > > > #Generated by Maven > > > #Thu Feb 21 21:53:42 PST 2008 > > > version=2.0.9-SNAPSHOT > > > groupId=org.apache.maven > > > artifactId=maven-core > > > > > > -- > > > > > > Our build system uses multiple plugins developed inhouse with > > > packaging type and forked lifecycle. > > > > > > > > > On Wed, Apr 2, 2008 at 2:52 PM, Brian E. Fox > > > wrote: > > > > > > > Thank you everyone for the testing and confirmatory responses so far. > > > > > > > It > > > > > > > helps to gauge the progress. There was one regression identified in > > > > 2.0.9 RC6: (MNG-3495: NPE at > > > > org.apache.maven.wagon.repository.Repository.hashCode). This has been > > > > fixed and RC7 posted. > > > > > > > > Various users have identified some issues with the site plugin that > > > > > > > seem > > > > > > > to occur when switching to 2.0.9. This can happen because we started > > > > locking down versions in 2.0.9. This is so if you haven't specified a > > > > version in your poms, it won't change on you going forward. This > > > > > > > means > > > > > > > that you will get upgraded to the latest site plugin (2.0-beta-6) > > > > > > > just > > > > > > > like you would if you did mvn -U on your build. If you have trouble > > > > > > > with > > > > > > > site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5 > > > > > > > in > > > > > > > your pom (we recommend locking your versions anyway). This is > > > > > > > preferable > > > > > > > to locking 2.0.9 to beta-5 for everyone and potentially forcing some > > > > people's versions backwards. > > > > > > > > In the future, only the most stable versions will be locked in the > > > > > > > super > > > > > > > pom and usually this will not be the most recent release. Since 2.0.9 > > > > was the first time we did this, we had to go with the current > > > > > > > versions > > > > > > > as the baseline. > > > > > > > > RC7 is available for download here: > > > > > > > > > > > > > > > > > > > > > > > che-maven/ > > > > > > > > > > > > Thank you for your assistance in testing the RCs. > > > > > > > > --Brian > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > > > For additional commands, e-mail: users-help@... > > > > > > > > > > > > > > > > > > > > > > > > -- > > > + Kaizer H. Sogiawala + > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > > For additional commands, e-mail: users-help@... > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscribe@... > > > For additional commands, e-mail: users-help@... > > > > > > > > > > > > > > > -- > > Brett Porter > > Blog: http://blogs.exist.com/bporter/ > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > For additional commands, e-mail: users-help@... > > > > > > > --- > John Casey > Committer and PMC Member, Apache Maven > mail: jdcasey at commonjava dot org > blog: http://www.ejlife.net/blogs/john > rss: http://feeds.feedburner.com/ejlife/john > > > -- + Kaizer H. Sogiawala + --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
RE: [2.0.9 RC8] Release Candidate testing
by tvworks
::
Rate this Message:
Brian,
Is there any documentation about the new "locked down" plugin in feature in 2.0.9? I would like to know how it works, how it impacts not having plugins locked vs. having them locked down already in your pom and how it would impact the enforcer plugin as well. Thanks. -----Original Message----- From: Brian E. Fox [mailto:brianf@...] Sent: Thursday, April 03, 2008 12:52 PM To: Maven Users List Cc: Maven Developers List Subject: [2.0.9 RC8] Release Candidate testing RC8 posted to solve this regression. http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/ -----Original Message----- From: Kaizer H. Sogiawala [mailto:kaizers@...] Sent: Thursday, April 03, 2008 2:51 PM To: Maven Users List Subject: Re: [2.0.9 RC7] Release Candidate testing I debugged through the source and can confirm "<directory>${basedir}</directory>" is the issue. On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jdcasey@...> wrote: > FWIW, using: > > <build> > <directory>${basedir}</directory> > </build> > > will express this error. See http://jira.codehaus.org/browse/MNG-3498 > > I have the fix, just need to get it cleaned up and committed. > > -john > > > > On Apr 3, 2008, at 11:23 AM, Brett Porter wrote: > > > > -1 could be empty string, and there were some hacks in the project > > builder that set expressions to that. I know that the path > > was effected by interpolation changes, even though indirectly, because > > the values got interpolated after instead of before. > > > > I'd look at those changes - though a POM that reproduces it is > > probably necessary to do so. > > > > - Brett > > > > On 04/04/2008, Brian E. Fox <brianf@...> wrote: > > > > > Do you have a way to reproduce this? The DefaultPathTranslator > > > hasn't changed since 2.0.6 so it must be a higher level change we're > > > looking for. > > > > > > > > > -----Original Message----- > > > From: Kaizer H. Sogiawala [mailto:kaizers@...] > > > Sent: Thursday, April 03, 2008 12:49 AM > > > To: Maven Users List > > > > > > Subject: Re: [2.0.9 RC7] Release Candidate testing > > > > > > I am getting a strange behavior with apache-maven-2.0.9-RC* (all > > > builds. Here is what I see- > > > > > > --- SNIP --- > > > + Error stacktraces are turned on. > > > Maven version: 2.0.9-RC7 > > > Java version: 1.5.0_12 > > > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > > > [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents > > > and Settings\blip\.m2\plugin-registry.xml' > > > [DEBUG] Building Maven global-level plugin registry from: 'C:\Program > > > Files\maven\bin\..\conf\plugin-registry.xml' > > > [INFO] Scanning for projects... > > > : > > > : *blip blip* > > > : > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [ERROR] FATAL ERROR > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [INFO] String index out of range: -1 > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [DEBUG] Trace > > > java.lang.StringIndexOutOfBoundsException: String index out of range: > -1 > > > at java.lang.String.substring(String.java:1768) > > > at java.lang.String.substring(String.java:1735) > > > at > > > > org.apache.maven.project.path.DefaultPathTranslator.stripBasedirToken(De > > > faultPathTranslator.java:101) > > > at > > > > org.apache.maven.project.path.DefaultPathTranslator.alignToBaseDirectory > > > (DefaultPathTranslator.java:82) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic( > > > DefaultMavenProjectBuilder.java:992) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul > > > tMavenProjectBuilder.java:867) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI > > > nternal(DefaultMavenProjectBuilder.java:495) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr > > > ojectBuilder.java:198) > > > at > > > org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) > > > at > > > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) > > > at > > > org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) > > > at > > > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > > > 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.jav > > > a:39) > > > at > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > > > Impl.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 Apr 02 21:40:25 PDT 2008 > > > [INFO] Final Memory: 1M/2M > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > > > --- SNIP --- > > > > > > This project is working fine with a 2.0.9-SNAPSHOT build with > > > following date/time stamp- > > > > > > #Generated by Maven > > > #Thu Feb 21 21:53:42 PST 2008 > > > version=2.0.9-SNAPSHOT > > > groupId=org.apache.maven > > > artifactId=maven-core > > > > > > -- > > > > > > Our build system uses multiple plugins developed inhouse with > > > packaging type and forked lifecycle. > > > > > > > > > On Wed, Apr 2, 2008 at 2:52 PM, Brian E. Fox > > > wrote: > > > > > > > Thank you everyone for the testing and confirmatory responses so far. > > > > > > > It > > > > > > > helps to gauge the progress. There was one regression identified in > > > > 2.0.9 RC6: (MNG-3495: NPE at > > > > org.apache.maven.wagon.repository.Repository.hashCode). This has been > > > > fixed and RC7 posted. > > > > > > > > Various users have identified some issues with the site plugin that > > > > > > > seem > > > > > > > to occur when switching to 2.0.9. This can happen because we started > > > > locking down versions in 2.0.9. This is so if you haven't specified a > > > > version in your poms, it won't change on you going forward. This > > > > > > > means > > > > > > > that you will get upgraded to the latest site plugin (2.0-beta-6) > > > > > > > just > > > > > > > like you would if you did mvn -U on your build. If you have trouble > > > > > > > with > > > > > > > site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5 > > > > > > > in > > > > > > > your pom (we recommend locking your versions anyway). This is > > > > > > > preferable > > > > > > > to locking 2.0.9 to beta-5 for everyone and potentially forcing some > > > > people's versions backwards. > > > > > > > > In the future, only the most stable versions will be locked in the > > > > > > > super > > > > > > > pom and usually this will not be the most recent release. Since 2.0.9 > > > > was the first time we did this, we had to go with the current > > > > > > > versions > > > > > > > as the baseline. > > > > > > > > RC7 is available for download here: > > > > > > > > > > > > > > > > > > > > > > > che-maven/ > > > > > > > > > > > > Thank you for your assistance in testing the RCs. > > > > > > > > --Brian > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > > > For additional commands, e-mail: users-help@... > > > > > > > > > > > > > > > > > > > > > > > > -- > > > + Kaizer H. Sogiawala + > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > > For additional commands, e-mail: users-help@... > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscribe@... > > > For additional commands, e-mail: users-help@... > > > > > > > > > > > > > > > -- > > Brett Porter > > Blog: http://blogs.exist.com/bporter/ > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > For additional commands, e-mail: users-help@... > > > > > > > --- > John Casey > Committer and PMC Member, Apache Maven > mail: jdcasey at commonjava dot org > blog: http://www.ejlife.net/blogs/john > rss: http://feeds.feedburner.com/ejlife/john > > > -- + Kaizer H. Sogiawala + --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
RE: [2.0.9 RC8] Release Candidate testing
by Brian E Fox
::
Rate this Message:
Jason, nothing written yet. The effect is the same as putting the
versions in the pluginManagement of your corp pom. If you have defined them in your poms then those will override the superpom. The enforcer rule walks the tree and does not look at the super pom so it will still tell you which plugins are not defined in your pom hierarchy. -----Original Message----- From: Jason Chaffee [mailto:jason_chaffee@...] Sent: Thursday, April 03, 2008 4:23 PM To: Maven Users List Cc: Maven Developers List Subject: RE: [2.0.9 RC8] Release Candidate testing Brian, Is there any documentation about the new "locked down" plugin in feature in 2.0.9? I would like to know how it works, how it impacts not having plugins locked vs. having them locked down already in your pom and how it would impact the enforcer plugin as well. Thanks. -----Original Message----- From: Brian E. Fox [mailto:brianf@...] Sent: Thursday, April 03, 2008 12:52 PM To: Maven Users List Cc: Maven Developers List Subject: [2.0.9 RC8] Release Candidate testing RC8 posted to solve this regression. http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa che-maven/ -----Original Message----- From: Kaizer H. Sogiawala [mailto:kaizers@...] Sent: Thursday, April 03, 2008 2:51 PM To: Maven Users List Subject: Re: [2.0.9 RC7] Release Candidate testing I debugged through the source and can confirm "<directory>${basedir}</directory>" is the issue. On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jdcasey@...> wrote: > FWIW, using: > > <build> > <directory>${basedir}</directory> > </build> > > will express this error. See http://jira.codehaus.org/browse/MNG-3498 > > I have the fix, just need to get it cleaned up and committed. > > -john > > > > On Apr 3, 2008, at 11:23 AM, Brett Porter wrote: > > > > -1 could be empty string, and there were some hacks in the project > > builder that set expressions to that. I know that the path > > was effected by interpolation changes, even though indirectly, because > > the values got interpolated after instead of before. > > > > I'd look at those changes - though a POM that reproduces it is > > probably necessary to do so. > > > > - Brett > > > > On 04/04/2008, Brian E. Fox <brianf@...> wrote: > > > > > Do you have a way to reproduce this? The DefaultPathTranslator > > > hasn't changed since 2.0.6 so it must be a higher level change we're > > > looking for. > > > > > > > > > -----Original Message----- > > > From: Kaizer H. Sogiawala [mailto:kaizers@...] > > > Sent: Thursday, April 03, 2008 12:49 AM > > > To: Maven Users List > > > > > > Subject: Re: [2.0.9 RC7] Release Candidate testing > > > > > > I am getting a strange behavior with apache-maven-2.0.9-RC* (all > > > builds. Here is what I see- > > > > > > --- SNIP --- > > > + Error stacktraces are turned on. > > > Maven version: 2.0.9-RC7 > > > Java version: 1.5.0_12 > > > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > > > [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents > > > and Settings\blip\.m2\plugin-registry.xml' > > > [DEBUG] Building Maven global-level plugin registry from: 'C:\Program > > > Files\maven\bin\..\conf\plugin-registry.xml' > > > [INFO] Scanning for projects... > > > : > > > : *blip blip* > > > : > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [ERROR] FATAL ERROR > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [INFO] String index out of range: -1 > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [DEBUG] Trace > > > java.lang.StringIndexOutOfBoundsException: String index out of range: > -1 > > > at java.lang.String.substring(String.java:1768) > > > at java.lang.String.substring(String.java:1735) > > > at > > > > org.apache.maven.project.path.DefaultPathTranslator.stripBasedirToken(De > > > faultPathTranslator.java:101) > > > at > > > > org.apache.maven.project.path.DefaultPathTranslator.alignToBaseDirectory > > > (DefaultPathTranslator.java:82) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic( > > > DefaultMavenProjectBuilder.java:992) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul > > > tMavenProjectBuilder.java:867) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI > > > nternal(DefaultMavenProjectBuilder.java:495) > > > at > > > > org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPr > > > ojectBuilder.java:198) > > > at > > > org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) > > > at > > > org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) > > > at > > > org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) > > > at > > > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) > > > 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.jav > > > a:39) > > > at > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > > > Impl.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 Apr 02 21:40:25 PDT 2008 > > > [INFO] Final Memory: 1M/2M > > > [INFO] > > > > ------------------------------------------------------------------------ > > > > > > --- SNIP --- > > > > > > This project is working fine with a 2.0.9-SNAPSHOT build with > > > following date/time stamp- > > > > > > #Generated by Maven > > > #Thu Feb 21 21:53:42 PST 2008 > > > version=2.0.9-SNAPSHOT > > > groupId=org.apache.maven > > > artifactId=maven-core > > > > > > -- > > > > > > Our build system uses multiple plugins developed inhouse with > > > packaging type and forked lifecycle. > > > > > > > > > On Wed, Apr 2, 2008 at 2:52 PM, Brian E. Fox > > > wrote: > > > > > > > Thank you everyone for the testing and confirmatory responses so far. > > > > > > > It > > > > > > > helps to gauge the progress. There was one regression identified in > > > > 2.0.9 RC6: (MNG-3495: NPE at > > > > org.apache.maven.wagon.repository.Repository.hashCode). This has been > > > > fixed and RC7 posted. > > > > > > > > Various users have identified some issues with the site plugin that > > > > > > > seem > > > > > > > to occur when switching to 2.0.9. This can happen because we started > > > > locking down versions in 2.0.9. This is so if you haven't specified a > > > > version in your poms, it won't change on you going forward. This > > > > > > > means > > > > > > > that you will get upgraded to the latest site plugin (2.0-beta-6) > > > > > > > just > > > > > > > like you would if you did mvn -U on your build. If you have trouble > > > > > > > with > > > > > > > site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5 > > > > > > > in > > > > > > > your pom (we recommend locking your versions anyway). This is > > > > > > > preferable > > > > > > > to locking 2.0.9 to beta-5 for everyone and potentially forcing some > > > > people's versions backwards. > > > > > > > > In the future, only the most stable versions will be locked in the > > > > > > > super > > > > > > > pom and usually this will not be the most recent release. Since 2.0.9 > > > > was the first time we did this, we had to go with the current > > > > > > > versions > > > > > > > as the baseline. > > > > > > > > RC7 is available for download here: > > > > > > > > > > > > > > > > > > > > > > > che-maven/ > > > > > > > > > > > > Thank you for your assistance in testing the RCs. > > > > > > > > --Brian > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > > > For additional commands, e-mail: users-help@... > > > > > > > > > > > > > > > > > > > > > > > > -- > > > + Kaizer H. Sogiawala + > > > > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > > For additional commands, e-mail: users-help@... > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscribe@... > > > For additional commands, e-mail: users-help@... > > > > > > > > > > > > > > > -- > > Brett Porter > > Blog: http://blogs.exist.com/bporter/ > > > > > > To unsubscribe, e-mail: users-unsubscribe@... > > For additional commands, e-mail: users-help@... > > > > > > > --- > John Casey > Committer and PMC Member, Apache Maven > mail: jdcasey at commonjava dot org > blog: http://www.ejlife.net/blogs/john > rss: http://feeds.feedburner.com/ejlife/john > > > -- + Kaizer H. Sogiawala + --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
signature.asc (196 bytes) 
| < Prev | 1 - 2 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |
