[jira] Created: (MEV-540) Please remove incorrectly copied snapshot directories for Groovy
Please remove incorrectly copied snapshot directories for Groovy Key: MEV-540 URL: http://jira.codehaus.org/browse/MEV-540 Project: Maven Evangelism Issue Type: Bug Reporter: Paul King The Groovy project uses an automatic codehaus scheme to copy its Maven 2 artifacts into the Maven repository. Any artifacts with SNAPSHOT in the version are copied to a local codehaus snapshot repository. Other version are synced with the Maven repository. I didn't realise that case was significant while trying to publish a snapshot release and it was incorrectly synced into the main repository. Could this be removed please. The non-snapshot, i.e. 1.1-beta-2 has since been published and should be left as is. Thanks, Paul. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2254) the encoding parameter in xml declaration of POM is ignored
[ http://jira.codehaus.org/browse/MNG-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-2254: --- Attachment: (was: MNG-2254.diff) > the encoding parameter in xml declaration of POM is ignored > > > Key: MNG-2254 > URL: http://jira.codehaus.org/browse/MNG-2254 > Project: Maven 2 > Issue Type: Bug > Components: POM::Encoding >Reporter: Naoki Nose >Assignee: Jason van Zyl > Fix For: 2.0.8 > > Attachments: DefaultMavenProjectBuilder.diff, MNG-2254.diff, > modello-plugin-xpp3.diff > > > DefaultMavenProjectBuilder reads POM in system default character encoding, > and the encoding parameter in xml declartion is ignored. > to fix this problem, We should > - fix modello-plugin-xpp3 to use the xml parser which is able to handle the > encoding parameter properly > - regenerate maven-model using fixed modello-plugin-xpp3 > - fix DefaultMavenProjectBuilder to use regenerated maven-model properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2254) the encoding parameter in xml declaration of POM is ignored
[ http://jira.codehaus.org/browse/MNG-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-2254: --- Attachment: MNG-2254.diff > the encoding parameter in xml declaration of POM is ignored > > > Key: MNG-2254 > URL: http://jira.codehaus.org/browse/MNG-2254 > Project: Maven 2 > Issue Type: Bug > Components: POM::Encoding >Reporter: Naoki Nose >Assignee: Jason van Zyl > Fix For: 2.0.8 > > Attachments: DefaultMavenProjectBuilder.diff, MNG-2254.diff, > modello-plugin-xpp3.diff > > > DefaultMavenProjectBuilder reads POM in system default character encoding, > and the encoding parameter in xml declartion is ignored. > to fix this problem, We should > - fix modello-plugin-xpp3 to use the xml parser which is able to handle the > encoding parameter properly > - regenerate maven-model using fixed modello-plugin-xpp3 > - fix DefaultMavenProjectBuilder to use regenerated maven-model properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2254) the encoding parameter in xml declaration of POM is ignored
[ http://jira.codehaus.org/browse/MNG-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-2254: --- Attachment: MNG-2254-2.diff Here is a new patch fixing encoding detection for pom.xml, settings.xml and profiles.xml > the encoding parameter in xml declaration of POM is ignored > > > Key: MNG-2254 > URL: http://jira.codehaus.org/browse/MNG-2254 > Project: Maven 2 > Issue Type: Bug > Components: POM::Encoding >Reporter: Naoki Nose >Assignee: Jason van Zyl > Fix For: 2.0.8 > > Attachments: DefaultMavenProjectBuilder.diff, MNG-2254-2.diff, > MNG-2254.diff, modello-plugin-xpp3.diff > > > DefaultMavenProjectBuilder reads POM in system default character encoding, > and the encoding parameter in xml declartion is ignored. > to fix this problem, We should > - fix modello-plugin-xpp3 to use the xml parser which is able to handle the > encoding parameter properly > - regenerate maven-model using fixed modello-plugin-xpp3 > - fix DefaultMavenProjectBuilder to use regenerated maven-model properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANTTASKS-79) add XML encoding support for pom.xml and settings.xml
add XML encoding support for pom.xml and settings.xml - Key: MANTTASKS-79 URL: http://jira.codehaus.org/browse/MANTTASKS-79 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: POM Integration Affects Versions: 2.0.7 Reporter: Herve Boutemy -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MANTTASKS-79) add XML encoding support for pom.xml and settings.xml
[ http://jira.codehaus.org/browse/MANTTASKS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MANTTASKS-79: --- Attachment: MANTTASKS-79.diff this patch treats settings.xml encoding for pom.xml encoding, everything is in MNG-2254 > add XML encoding support for pom.xml and settings.xml > - > > Key: MANTTASKS-79 > URL: http://jira.codehaus.org/browse/MANTTASKS-79 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: POM Integration >Affects Versions: 2.0.7 >Reporter: Herve Boutemy > Attachments: MANTTASKS-79.diff > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MANTTASKS-79) add XML encoding support for pom.xml and settings.xml
[ http://jira.codehaus.org/browse/MANTTASKS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MANTTASKS-79: --- Fix Version/s: 2.0.8 Patch Submitted: [Yes] > add XML encoding support for pom.xml and settings.xml > - > > Key: MANTTASKS-79 > URL: http://jira.codehaus.org/browse/MANTTASKS-79 > Project: Maven 2.x Ant Tasks > Issue Type: Bug > Components: POM Integration >Affects Versions: 2.0.7 >Reporter: Herve Boutemy > Fix For: 2.0.8 > > Attachments: MANTTASKS-79.diff > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MIDEA-98) Module filepath is generated incorrectly
[ http://jira.codehaus.org/browse/MIDEA-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MIDEA-98. Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: 2.2 Fixed in SVN r556436. > Module filepath is generated incorrectly > > > Key: MIDEA-98 > URL: http://jira.codehaus.org/browse/MIDEA-98 > Project: Maven 2.x IDEA Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: $ mvn -v > Maven version: 2.0.7 > Java version: 1.5.0_11 > OS name: "windows xp" version: "5.1" arch: "x86" > cygwin >Reporter: Ben Hood >Assignee: Dennis Lundberg > Fix For: 2.2 > > Attachments: toRelative-2.out, toRelative.out > > > I have a multi-module mvn project. > When I do an mvn idea:clean idea:idea, the following ProjectModuleManager > snippet in the top level .ipr is generated: > > > > >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml"/> > > > The $PROJECT_DIR in this case is C:/dev/voca/gateway/. > But this path is being appended in a hard-coded fashion after the > $PROJECT_DIR entry. > The symptom in Intellij is the following error message: > Cannot load module: File > C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not > exist > Would you like to remove the module from the project? > The workaround is to delete the extra appended file path from each module > entry in the above mentioned snippet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MIDEA-98) Module filepath is generated incorrectly
[ http://jira.codehaus.org/browse/MIDEA-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MIDEA-98: - Environment: $ mvn -v Maven version: 2.0.7 Java version: 1.5.0_11 OS name: "windows xp" version: "5.1" arch: "x86" cygwin was: $ mvn -v Maven version: 2.0.7 Java version: 1.5.0_11 OS name: "windows xp" version: "5.1" arch: "x86" > Module filepath is generated incorrectly > > > Key: MIDEA-98 > URL: http://jira.codehaus.org/browse/MIDEA-98 > Project: Maven 2.x IDEA Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: $ mvn -v > Maven version: 2.0.7 > Java version: 1.5.0_11 > OS name: "windows xp" version: "5.1" arch: "x86" > cygwin >Reporter: Ben Hood > Fix For: 2.2 > > Attachments: toRelative-2.out, toRelative.out > > > I have a multi-module mvn project. > When I do an mvn idea:clean idea:idea, the following ProjectModuleManager > snippet in the top level .ipr is generated: > > > > >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml"/> >filepath="$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml"/> > > > The $PROJECT_DIR in this case is C:/dev/voca/gateway/. > But this path is being appended in a hard-coded fashion after the > $PROJECT_DIR entry. > The symptom in Intellij is the following error message: > Cannot load module: File > C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not > exist > Would you like to remove the module from the project? > The workaround is to delete the extra appended file path from each module > entry in the above mentioned snippet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-127) Ability to add other workspace configuration similar to add-maven-repo goal
[ http://jira.codehaus.org/browse/MECLIPSE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102321 ] Dan Tran commented on MECLIPSE-127: --- committed at rev 556442 the attached patch, as well as the fix for ECLIPSE-296. Tested the build with both windows and solaris platforms. > Ability to add other workspace configuration similar to add-maven-repo goal > --- > > Key: MECLIPSE-127 > URL: http://jira.codehaus.org/browse/MECLIPSE-127 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Affects Versions: 2.2 > Environment: xp >Reporter: Dan Tran > Fix For: 2.5 > > Attachments: MECLIPSE-127.diff > > > add ability to configure code slyle, jvm, warning,etc > We can create a new goal like eclipse:configure-workspace and merge > add-maven-repo into it. > We will need to a complex class for injection. This complex class will have > the following property >String workspaceDirectory; // if given, will trigger add-maven-repo >String styleFile; // if given, will trigger the settup of source format > style file >etc, > This will allow us to preconfigure eclispe configuration in the parent pom, > and there for developers in a team will have the > same eclipse setup, rather manually configure it. > WDYT? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work logged: (MECLIPSE-127) Ability to add other workspace configuration similar to add-maven-repo goal
[ http://jira.codehaus.org/browse/MECLIPSE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_102322 ] Dan Tran logged work on MECLIPSE-127: - Time Logged: 2 days Time Spent: 2 days Remaining Estimate: 0 minutes > Ability to add other workspace configuration similar to add-maven-repo goal > --- > > Key: MECLIPSE-127 > URL: http://jira.codehaus.org/browse/MECLIPSE-127 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Affects Versions: 2.2 > Environment: xp >Reporter: Dan Tran > Fix For: 2.5 > > Attachments: MECLIPSE-127.diff > > Time Spent: 2 days > Remaining Estimate: 0 minutes > > add ability to configure code slyle, jvm, warning,etc > We can create a new goal like eclipse:configure-workspace and merge > add-maven-repo into it. > We will need to a complex class for injection. This complex class will have > the following property >String workspaceDirectory; // if given, will trigger add-maven-repo >String styleFile; // if given, will trigger the settup of source format > style file >etc, > This will allow us to preconfigure eclispe configuration in the parent pom, > and there for developers in a team will have the > same eclipse setup, rather manually configure it. > WDYT? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-127) Ability to add other workspace configuration similar to add-maven-repo goal
[ http://jira.codehaus.org/browse/MECLIPSE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed MECLIPSE-127. - Assignee: Dan Tran Resolution: Fixed > Ability to add other workspace configuration similar to add-maven-repo goal > --- > > Key: MECLIPSE-127 > URL: http://jira.codehaus.org/browse/MECLIPSE-127 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Affects Versions: 2.2 > Environment: xp >Reporter: Dan Tran >Assignee: Dan Tran > Fix For: 2.5 > > Attachments: MECLIPSE-127.diff > > Time Spent: 2 days > Remaining Estimate: 0 minutes > > add ability to configure code slyle, jvm, warning,etc > We can create a new goal like eclipse:configure-workspace and merge > add-maven-repo into it. > We will need to a complex class for injection. This complex class will have > the following property >String workspaceDirectory; // if given, will trigger add-maven-repo >String styleFile; // if given, will trigger the settup of source format > style file >etc, > This will allow us to preconfigure eclispe configuration in the parent pom, > and there for developers in a team will have the > same eclipse setup, rather manually configure it. > WDYT? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-296) Wrong generated source-path when warSourceDirectory is set
[
http://jira.codehaus.org/browse/MECLIPSE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Tran closed MECLIPSE-296.
-
Assignee: Dan Tran
Resolution: Fixed
committed the fix togetter with MECLIPSE-127 where
IdeUtils.toRelativeAndFixSeparator must convert 'fileToAdd' to absolute path
base on project directory
> Wrong generated source-path when warSourceDirectory is set
> --
>
> Key: MECLIPSE-296
> URL: http://jira.codehaus.org/browse/MECLIPSE-296
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
>Affects Versions: 2.4
> Environment: xp
>Reporter: Dan Tran
>Assignee: Dan Tran
> Fix For: 2.5
>
>
> When warSourceDirectory of the war configuration is explicitly set relative
> to project basedir, its source-path is incorrectly set in reactor mode.
> The path is constructed using the reactor's basedir + warSourceDirectory. It
> must be project's basedir + warSourceDirectory
> The work around is to set warSourceDirectory using absolute path
> here is the configuration to reproduce the issue
>
> maven-war-plugin
>
> webapp
>
>
> the incorrected source-path is in ..settings\org.eclipse.wst.common.component
> The work around is
>
> maven-war-plugin
>
> ${basedir}/webapp
>
>
> The main problem in code is in IdeUtils.getCanonicalPath() returns incorrect
> path in reactor mode.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MIDEA-100) Module file (.iml) is generated in a way that sources and javadocs are not recognized by Intellij Idea
[
http://jira.codehaus.org/browse/MIDEA-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102324
]
Gerhard Mueller commented on MIDEA-100:
---
This is really strange. I really had that problem, reproducable on my computer.
Today I did the same:
mvn -U idea:idea -DdownloadSources=true -DdownloadJavadocs=true
, and now I get the following (part of .iml file):
I will attach my pom file, slightly changed because of private information, and
the generated files.
> Module file (.iml) is generated in a way that sources and javadocs are not
> recognized by Intellij Idea
> --
>
> Key: MIDEA-100
> URL: http://jira.codehaus.org/browse/MIDEA-100
> Project: Maven 2.x IDEA Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: WIndows XP, Maven 2.0.7, Java 1.6, IntelliJ IDEA 7.0M1b
>Reporter: Gerhard Mueller
>Priority: Critical
>
> When a new iml file is generated with mvn idea:idea -DdownloadSources=true
> -DdownloadJavadocs=true
> the generated .iml-file contains invalid entries for the javadocs and
> sources, like in this example:
>
>
>
>
>
> />
>
>
> />
>
>
> />
>
>
>
> Removing the empty
>
>
> entries allows me to see the sources, but this is not a good solution.
> By looking at the source code
> https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-idea-plugin/src/main/java/org/apache/maven/plugin/idea/IdeaModuleMojo.java
> the reason might be the method
> private Element createOrGetElement( Element lib, String name )
> {
> Element el = lib.element( "name" );
> if ( el == null )
> {
> el = createElement( lib, name );
> }
> return el;
> }
> In my opinion, the method should look like this:
>
> private Element createOrGetElement( Element lib, String name )
> {
> Element el = lib.element( name ); // CHANGE DONE HERE
> if ( el == null )
> {
> el = createElement( lib, name );
> }
> return el;
> }
> as otherwiese ALWAYS new element instances are created, regardless the
> provided name to look for,
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MIDEA-100) Module file (.iml) is generated in a way that sources and javadocs are not recognized by Intellij Idea
[
http://jira.codehaus.org/browse/MIDEA-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Mueller updated MIDEA-100:
--
Attachment: idea-demo-project.zip
The demo project (pom file and generated idea project files) which show that
the generation of idea files seems to have a problem
> Module file (.iml) is generated in a way that sources and javadocs are not
> recognized by Intellij Idea
> --
>
> Key: MIDEA-100
> URL: http://jira.codehaus.org/browse/MIDEA-100
> Project: Maven 2.x IDEA Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: WIndows XP, Maven 2.0.7, Java 1.6, IntelliJ IDEA 7.0M1b
>Reporter: Gerhard Mueller
>Priority: Critical
> Attachments: idea-demo-project.zip
>
>
> When a new iml file is generated with mvn idea:idea -DdownloadSources=true
> -DdownloadJavadocs=true
> the generated .iml-file contains invalid entries for the javadocs and
> sources, like in this example:
>
>
>
>
>
> />
>
>
> />
>
>
> />
>
>
>
> Removing the empty
>
>
> entries allows me to see the sources, but this is not a good solution.
> By looking at the source code
> https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-idea-plugin/src/main/java/org/apache/maven/plugin/idea/IdeaModuleMojo.java
> the reason might be the method
> private Element createOrGetElement( Element lib, String name )
> {
> Element el = lib.element( "name" );
> if ( el == null )
> {
> el = createElement( lib, name );
> }
> return el;
> }
> In my opinion, the method should look like this:
>
> private Element createOrGetElement( Element lib, String name )
> {
> Element el = lib.element( name ); // CHANGE DONE HERE
> if ( el == null )
> {
> el = createElement( lib, name );
> }
> return el;
> }
> as otherwiese ALWAYS new element instances are created, regardless the
> provided name to look for,
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-266) plugin applies java facet to ear project
[ http://jira.codehaus.org/browse/MECLIPSE-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102327 ] Srepfler Srgjan commented on MECLIPSE-266: -- Hi Thierry, I agree with most points in your comment, I also have the feeling it will take some time as making new artifacts is always a time consuming issue and with stretched resources low priority issues don't get the right measure of care. I did not understand the ant use case but I don't have any issue with that. As far as my project is concerned, I personally dropped the use of eclipse a while ago because of validations issues one of which is filed with this bug. This bug is one pain it the behind but I personally don't find it critical. As I said I fix this problem by editing the file by hand and removing the java facet. My project builds fine with maven and having this issue fixed would only help me in being able to use it with eclipse friction free. Of course I would say that not too many people use maven and eclipse together, otherwise this issue would have been noticed earlier and fixed by now (I've noticed this issue perhaps a year ago and filed this bug only recently, I still don't understand what were people doing in the mean time). > plugin applies java facet to ear project > > > Key: MECLIPSE-266 > URL: http://jira.codehaus.org/browse/MECLIPSE-266 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.3 > Environment: Windows XP >Reporter: Srepfler Srgjan > > In .settings/org.eclipse.wst.common.project.facet.core.xml of the EAR module > I'm getting this: > > > > > > > This is a wrong facet on a EAR module and I can't compile if I don't edit > this file manually (I can't do it from the project properties - facets dialog) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-1317) Builds hand when JUNIT assertion failure text > 8192 characters
[ http://jira.codehaus.org/browse/CONTINUUM-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1317. --- Assignee: Emmanuel Venisse Resolution: Duplicate Fix Version/s: (was: 1.1-beta-2) > Builds hand when JUNIT assertion failure text > 8192 characters > --- > > Key: CONTINUUM-1317 > URL: http://jira.codehaus.org/browse/CONTINUUM-1317 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-alpha-2 >Reporter: Bryan Madsen >Assignee: Emmanuel Venisse >Priority: Critical > > The output file for the build shows the project has completed building yet > the display in the project page show the project stuck in a building state. > Exception follows: > 2450900 [Thread-6] ERROR > org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - > Error executing task > edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: > javax.jdo.JDOFatalUserException: Attempt to store value > "org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error > executing action 'execute-builder' > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:432) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:145) > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) > at > edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) > at > edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) > at java.lang.Thread.run(Thread.java:595) > Caused by: javax.jdo.JDOFatalUserException: Attempt to store value > "junit.framework.AssertionFailedError: Line does not contain expected text > ... > at junit.framework.Assert.fail(Assert.java:47) > at junit.framework.Assert.assertTrue(Assert.java:20) > at > com.cerner.msvc.signatureline.SignatureLineManagerTest.test199535_AllSupportedElements(SignatureLineManagerTest.java:440) > " in column "EXCEPTIONSTRING" that has maximum length of 8192. Please correct > your data! > at > org.jpox.store.rdbms.mapping.CharRDBMSMapping.setString(CharRDBMSMapping.java:214) > at > org.jpox.store.mapping.SingleFieldMapping.setString(SingleFieldMapping.java:203) > at > org.jpox.store.rdbms.fieldmanager.ParameterSetter.storeStringField(ParameterSetter.java:122) > at > org.jpox.state.StateManagerImpl.providedStringField(StateManagerImpl.java:2757) > at > org.apache.maven.continuum.model.scm.TestCaseFailure.jdoProvideField(TestCaseFailure.java) > at > org.apache.maven.continuum.model.scm.TestCaseFailure.jdoProvideFields(TestCaseFailure.java) > at > org.jpox.state.StateManagerImpl.provideFields(StateManagerImpl.java:3115) > at > org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:252) > at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) > at org.jpox.store.StoreManager.insert(StoreManager.java:920) > at > org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667) > at > org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646) > at > org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1198) > at > org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1243) > at > org.jpox.store.rdbms.scostore.FKListStore.validateElementForWriting(FKListStore.java:1231) > at > org.jpox.store.rdbms.scostore.FKListStore.internalAdd(FKListStore.java:772) > at > org.jpox.store.rdbms.scostore.AbstractListStore.addAll(AbstractListStore.java:386) > at > org.jpox.store.mapping.CollectionMapping.postInsert(CollectionMapping.java:209) > at > org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:464) > at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2519) > at org.jpox.store.StoreManager.insert(StoreManager.java:920) > at > org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3667) > at > org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3646) > at > org.jpox.AbstractPersist
[jira] Closed: (CONTINUUM-709) Runtime error during recording in datanase
[ http://jira.codehaus.org/browse/CONTINUUM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-709. -- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: (was: 1.1-beta-2) 1.1-beta-1 > Runtime error during recording in datanase > -- > > Key: CONTINUUM-709 > URL: http://jira.codehaus.org/browse/CONTINUUM-709 > Project: Continuum > Issue Type: Bug > Components: Core system, Database >Affects Versions: 1.0.3 > Environment: solaris 9 >Reporter: Olivier Lamy >Assignee: Emmanuel Venisse > Fix For: 1.1-beta-1 > > > I have the following strack trace : > ERROR 22001: A truncation error was encountered trying to shrink VARCHAR > '/OTAReceiver/trunk/ota-rec > eiver-parsing/src/main/java/com/ac&' to length 255. > at org.apache.derby.iapi.error.StandardException.newException(Unknown > Source) > at org.apache.derby.iapi.types.SQLChar.hasNonBlankChars(Unknown > Source) > at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) > at org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) > at org.apache.derby.iapi.types.DataTypeDescriptor.normalize(Unknown > Source) > at > org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeRow(Unknown > Source) > at > org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Unknown > Source) > at > org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(Unknown > Source) > at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown > Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown > Source) > at org.jpox.store.rdbms.request.Request.executeUpdate(Request.java:78) > at > org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:258) > at org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2146) > at org.jpox.store.StoreManager.insert(StoreManager.java:739) > at > org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3415) > at > org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3388) > at > org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.jav > a:1146) > at > org.jpox.AbstractPersistenceManager.makePersistent(AbstractPersistenceManager.java:1201) > at > org.codehaus.plexus.jdo.PlexusJdoUtils.makePersistent(PlexusJdoUtils.java:97) > at > org.apache.maven.continuum.store.JdoContinuumStore.makePersistent(JdoContinuumStore.java: > 524) > at > org.apache.maven.continuum.store.JdoContinuumStore.addBuildResult(JdoContinuumStore.java: > 265) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.makeAndStoreBuildResult > (DefaultBuildController.java:443) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildContr > oller.java:298) > The result is strange : > - in the build history the build is marked as succesfull > - in the project summary I have the red icon which says failed but no mail > received > -- > Olivier -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-837) POM upload screen says file:// URLs are supported but fails if you try one
[ http://jira.codehaus.org/browse/CONTINUUM-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-837. -- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: (was: 1.1-beta-2) 1.1-alpha-2 we dont have this message in alpha-2 > POM upload screen says file:// URLs are supported but fails if you try one > -- > > Key: CONTINUUM-837 > URL: http://jira.codehaus.org/browse/CONTINUUM-837 > Project: Continuum > Issue Type: Bug > Components: Web interface >Affects Versions: 1.0.3 >Reporter: Aaron Mulder >Assignee: Emmanuel Venisse > Fix For: 1.1-alpha-2 > > > The POM upload screen lists file:// among the supported URL types. However, > any file:// URL that you try results in a misleading error message. > In fact, the "file" protocol is disabled by default. > This screen should explain that "file" must be manually enabled, and the > resulting error message should say that the "file" protocol is disabled. > Ideally it would point you to the correct place to enable it, and mention > that until you've started continuum for the first time, the config file you > need to edit won't be there (the JAR has to be unpacked first). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-1107) Continuum build failes in continuum-core on a clean system
[ http://jira.codehaus.org/browse/CONTINUUM-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed CONTINUUM-1107. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: (was: 1.1-beta-2) 1.1-alpha-2 > Continuum build failes in continuum-core on a clean system > -- > > Key: CONTINUUM-1107 > URL: http://jira.codehaus.org/browse/CONTINUUM-1107 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.1-alpha-1 >Reporter: Roald Bankras >Assignee: Emmanuel Venisse > Fix For: 1.1-alpha-2 > > Attachments: > org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.txt > > > MavenTwoContinuumProjectBuilderTest failes twice: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (NMAVEN-78) Swap files are copied as build test sources
[ http://jira.codehaus.org/browse/NMAVEN-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102347 ] Evan Worley commented on NMAVEN-78: --- Patch applied and integration tests added, all works great, thanks for the work Brian and Amol! > Swap files are copied as build test sources > --- > > Key: NMAVEN-78 > URL: http://jira.codehaus.org/browse/NMAVEN-78 > Project: NMaven > Issue Type: Bug > Environment: Maven 2.0.6, NMaven 0.14-SNAPSHOT, Windows >Reporter: Evan Worley >Priority: Trivial > Attachments: NMAVEN-78.diff > > > When the NMaven copies the test source to target/build-test-sources it copies > too many files including *.swp files. One solution might be to only copy .cs > files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (NMAVEN-78) Swap files are copied as build test sources
[ http://jira.codehaus.org/browse/NMAVEN-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Worley closed NMAVEN-78. - Resolution: Fixed Patch solved issue > Swap files are copied as build test sources > --- > > Key: NMAVEN-78 > URL: http://jira.codehaus.org/browse/NMAVEN-78 > Project: NMaven > Issue Type: Bug > Environment: Maven 2.0.6, NMaven 0.14-SNAPSHOT, Windows >Reporter: Evan Worley >Priority: Trivial > Attachments: NMAVEN-78.diff > > > When the NMaven copies the test source to target/build-test-sources it copies > too many files including *.swp files. One solution might be to only copy .cs > files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
