[jira] Created: (CONTINUUM-1036) Allow continuum-rpc-client to accept project URL as parameter to add project
Allow continuum-rpc-client to accept project URL as parameter to add project Key: CONTINUUM-1036 URL: http://jira.codehaus.org/browse/CONTINUUM-1036 Project: Continuum Issue Type: Improvement Components: XMLRPC Interface Reporter: Valerie Lavilla -- 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: (MSUREFIRE-123) unable to establish my own http protocol handler for unit tests
[ http://jira.codehaus.org/browse/MSUREFIRE-123?page=comments#action_82035 ] Markus Waserscaff commented on MSUREFIRE-123: - Hi, when forking enabled, the system properties are not set on the command line, but programmatically. Could this be the problem? I have a similar problem and I can load my custom Handler class programmatically, but it is not properly registered and thus not activated. Is there a good reason why the system properties are set via System.setProperty() and not on the command line with -D...=...? > unable to establish my own http protocol handler for unit tests > --- > > Key: MSUREFIRE-123 > URL: http://jira.codehaus.org/browse/MSUREFIRE-123 > Project: Maven 2.x Surefire Plugin > Issue Type: Bug >Affects Versions: 2.2 > Environment: jse 5.0 (osx) >Reporter: Andy Fyfe > Fix For: 2.3 > > Attachments: protocol.zip > > > In order to establish my own http protocol handler, I set the system property > java.protocol.handler.pkgs and ensure that the tests require a fork. The > test runs fine under maven 1.0.2, but fails under maven 2.0.4. I have tried > both surefire 2.1.3 and 2.2, and both with the childDelegation option. > The test sees the system property properly set, but the test's protocol > handler is not actually used. > The attached zip file demonstrates this problem (run "maven test" and "mvn > test"). -- 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: (MECLIPSE-205) REISSUING: It should be possible to add additional classpath entries in plugin configuration (MECLIPSE-41)
REISSUING: It should be possible to add additional classpath entries in plugin configuration (MECLIPSE-41) -- Key: MECLIPSE-205 URL: http://jira.codehaus.org/browse/MECLIPSE-205 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Amit Kasher The following scenario demonstrates the issue: 1. Project A is managed by maven and it depends on project B which is not managed by maven. The dependency is with the logical scope of "compile". 2. Using maven's install:install-file plugin, project B's JAR file is installed in the repository. 3. Project A is set to depend on this JAR file in its POM (compile scope). 4. Both projects are developed in the same eclipse repository. The problem is that when classes in project B are changed, the only way to see these changes when developing project A is to regenerate project B's jar, install it in maven's repository and refresh project A. The ideal solution would be to set eclipse's plugin's configuration in project A's pom to something like this: .. .. src /projectB com.myprojects projectB 1.0 -- 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: (CONTINUUM-1036) Allow continuum-rpc-client to accept project URL as parameter to add project
[ http://jira.codehaus.org/browse/CONTINUUM-1036?page=all ] Valerie Lavilla updated CONTINUUM-1036: --- Attachment: CONTINUUM-1036-continuum-rpc-client.patch Added addProjectByURL method that accepts project URL and executor ID as parameters. Tested using maven2 project. > Allow continuum-rpc-client to accept project URL as parameter to add project > > > Key: CONTINUUM-1036 > URL: http://jira.codehaus.org/browse/CONTINUUM-1036 > Project: Continuum > Issue Type: Improvement > Components: XMLRPC Interface >Reporter: Valerie Lavilla > Attachments: CONTINUUM-1036-continuum-rpc-client.patch > > -- 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: (MAVENUPLOAD-1266) javassist 3.4.ga
javassist 3.4.ga Key: MAVENUPLOAD-1266 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1266 Project: maven-upload-requests Issue Type: Task Reporter: Koichi Kobayashi javassist 3.4.ga -- 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-1036) Allow continuum-rpc-client to accept project URL as parameter to add project
[ http://jira.codehaus.org/browse/CONTINUUM-1036?page=all ] Emmanuel Venisse closed CONTINUUM-1036. --- Assignee: Emmanuel Venisse Resolution: Fixed Fix Version/s: 1.1 Applied with some modifications. Thanks > Allow continuum-rpc-client to accept project URL as parameter to add project > > > Key: CONTINUUM-1036 > URL: http://jira.codehaus.org/browse/CONTINUUM-1036 > Project: Continuum > Issue Type: Improvement > Components: XMLRPC Interface >Reporter: Valerie Lavilla > Assigned To: Emmanuel Venisse > Fix For: 1.1 > > Attachments: CONTINUUM-1036-continuum-rpc-client.patch > > -- 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: (MPH-14) Add a mojo to print the dependency tree
[ http://jira.codehaus.org/browse/MPH-14?page=all ] fabrizio giustina closed MPH-14. Assignee: fabrizio giustina Resolution: Fixed Fix Version/s: 2.1 Patch committed, thans Mark > Add a mojo to print the dependency tree > --- > > Key: MPH-14 > URL: http://jira.codehaus.org/browse/MPH-14 > Project: Maven 2.x Help Plugin > Issue Type: New Feature >Reporter: Kenney Westerhof > Assigned To: fabrizio giustina >Priority: Minor > Fix For: 2.1 > > Attachments: MPH-14-patch.txt > > > This mojo should print a tree like is now on the dependencies report > generated by the site plugin. > This is more user-friendly than having to run with -X and grepping through > the huge amount of debug output. -- 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: (MNG-2693) Error executing post-site: java.util.MissingResourceException: Can't find bundle for base name site-plugin, locale en
Error executing post-site: java.util.MissingResourceException: Can't find bundle for base name site-plugin, locale en - Key: MNG-2693 URL: http://jira.codehaus.org/browse/MNG-2693 Project: Maven 2 Issue Type: Bug Components: Sites & Reporting Affects Versions: 2.1 Reporter: Stepan Roh I use Maven 2.1 embedder - if I build it from current SVN HEAD of maven-components (together with all components), I get this exception if I try to execute post-site: Caused by: org.apache.maven.reactor.MavenExecutionException: Error executing project within the reactor at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:214) at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:797) ... 19 more Caused by: java.util.MissingResourceException: Can't find bundle for base name site-plugin, locale en at org.codehaus.plexus.i18n.DefaultI18N.cacheBundle(DefaultI18N.java:394) at org.codehaus.plexus.i18n.DefaultI18N.getBundle(DefaultI18N.java:157) at org.codehaus.plexus.i18n.DefaultI18N.getString(DefaultI18N.java:206) at org.apache.maven.plugins.site.AbstractSiteMojo.populateReportsMenu(AbstractSiteMojo.java:400) at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.locateDocuments(AbstractSiteRenderingMojo.java:587) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:113) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:438) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:391) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:178) ... 21 more If I try revision 480835, it works. I see that there are some classworlds and container changes since that revision, so it can be related to that. -- 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: (MNGECLIPSE-138) "Unable to index" error
[ http://jira.codehaus.org/browse/MNGECLIPSE-138?page=comments#action_82192
]
David Win commented on MNGECLIPSE-138:
--
I am having the same exact issue
Whenever I add a dependency (such as antrun or the jboss plugin), the goals
pertaining to those plugins do not show up in the m2 builder.
help would be much apperciated.
> "Unable to index" error
> ---
>
> Key: MNGECLIPSE-138
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-138
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Components: Repository Management
>Affects Versions: 0.0.9
> Environment: Eclipse 3.2RC4a, Windows XP
>Reporter: Daniel Serodio
>
> I'm trying to "mavenize" an existing Eclipse project.
> After I added a joda-time 1.2.1 dependency to my project, m2eclipse
> downloaded it, but printed an error:
> Unable to index joda-time/joda-time/1.2.1/joda-time-1.2.1.jar; Cannot
> delete C:\Documents and
> Settings\dserodio\Desktop\projetos\.metadata\.plugins\org.maven.ide.eclipse\index\local\_s.cfs
> Then, I tried to add another dependency, but now, when I type anything in the
> "Repository Search" dialog, it shows an error on the dialog's
> bottom:
> Search error: C:\Documents and
> Settings\dserodio\Desktop\projetos\.metadata\.plugins\org.maven.ide.eclipse\index\local\segments
> (File not found)
> I searched for this file ({{segments}}) and it really doesn't exist.
> I disabled Maven2 for the project, deleted {{pom.xml}}, closed Eclipse,
> deleted the {{.metadata\.plugins\org.maven.ide.eclipse}}, opened Eclipse
> again and retried, and got the exact same error.
> Eclipse's error log doesn't contain anything maven-related.
--
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: (MRELEASE-178) Release prepare fails to update version information for ejb-client dependencies
[ http://jira.codehaus.org/browse/MRELEASE-178?page=comments#action_82199 ] Eric Bernstein commented on MRELEASE-178: - Jason, any chance of this getting included in 2.0-beta-5? Currently, I'm maintaining my own branch of the code for my company to use. I'd love to drop our release plugin in favor of the official one when 2.0-beta-5 is released. > Release prepare fails to update version information for ejb-client > dependencies > --- > > Key: MRELEASE-178 > URL: http://jira.codehaus.org/browse/MRELEASE-178 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 >Reporter: Eric Bernstein > Attachments: MRELEASE-178-similar-deps.patch > > > If you use the dependency management section of a parent pom to include > sub-poms of the same project, the release plugin will update the version > number for those projects as part of the prepare phase. > Unfortunately, if you have two dependencies with the same groupId and > artifactId (as is the case with generated ejb-clients) prepare will just > update one of them. > I believe the problem in the code is in > AbstractRewritePomsPhase.updateDomVersion. The code currently uses an xpath > expression matching on groupId and artifactId and then calls > xpath.getSingleNode to find the object to update. This will leave out one of > the dependencies (either ejb or ejb-client). > I'm having a little trouble writing a unit test for this (hence no patch > upload), but if I could do that, I believe the fix would either be looping > over the elements returned from the xpath expression, or altering the xpath > expression (and the rest of the artifact handling - read: bigger change) to > be more explicit about what artifacts it's looking at (including type, > classifier, etc...). -- 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: (MNG-2363) does not work in a multi-project build
[ http://jira.codehaus.org/browse/MNG-2363?page=comments#action_82200 ]
Ryan Slobojan commented on MNG-2363:
Similar situation, similar result for us. We are trying to only activate a
profile on a submodule of a reactor build, and the one-time evaluation makes
this impossible.
Has a fix for this issue been implemented or considered? I see that the fix
version is currently 2.1, but is that wishful thinking or will this bug
actually be addressed in 2.1? We would prefer if it could be addressed in 2.0.5
if possible, in order to get a fix sooner rather than later for this issue.
> does not work in a multi-project build
> ---
>
> Key: MNG-2363
> URL: http://jira.codehaus.org/browse/MNG-2363
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Reporter: David Boden
>Priority: Critical
> Fix For: 2.1
>
> Attachments: problemactivation.zip, screenshot-1.jpg
>
>
> I would expect each subproject to have the profile turned on or off depending
> on whether ${basedir}/file-to-check-for exists.
> Instead, during a multi-project build the profile is either on or off
> depending on whether the file exists relative to the *aggregator pom*. The
> decision is made once.
> Variable substitution doesn't work, so I can't explicitly use
> ${basedir}/file-to-check-for or any variation on this theme
> to workaround the bug.
> Some background to my particular problem. I have 10 modules to build. Some of
> them are GUI modules and contain a file called plugin.xml in the subproject
> directory. I want to package these up specially and sign them, ready for
> deployment to webstart. The other modules are shared and server code and I
> don't want these packaged in the same way. So, I've got a dependency in my
> *parent* pom file which activates a profile called "guibundle" if a
> plugin.xml file exists in the subproject directory.
--
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: (MPWAR-68) corrupt images after copy
[ http://jira.codehaus.org/browse/MPWAR-68?page=all ] Arnaud Heritier updated MPWAR-68: - Fix Version/s: 1.6.3 > corrupt images after copy > - > > Key: MPWAR-68 > URL: http://jira.codehaus.org/browse/MPWAR-68 > Project: maven-war-plugin > Issue Type: Bug >Affects Versions: 1.6.2 >Reporter: G.J. Sterenborg > Fix For: 1.6.3 > > Attachments: descending.gif, descending.gif, descending.gif > > > maven-1.1-beta-3 seems to corrupt images during a . > I'll attach two samples: > - corrupt-copy (2284 bytes) > - original (843 bytes) -- 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] Moved: (MPWAR-68) corrupt images after copy
[ http://jira.codehaus.org/browse/MPWAR-68?page=all ] Arnaud Heritier moved MAVEN-1815 to MPWAR-68: - Affects Version/s: (was: 1.1-beta-3) 1.6.2 Workflow: jira (was: Maven New) Key: MPWAR-68 (was: MAVEN-1815) Project: maven-war-plugin (was: Maven 1.x) > corrupt images after copy > - > > Key: MPWAR-68 > URL: http://jira.codehaus.org/browse/MPWAR-68 > Project: maven-war-plugin > Issue Type: Bug >Affects Versions: 1.6.2 >Reporter: G.J. Sterenborg > Fix For: 1.6.3 > > Attachments: descending.gif, descending.gif, descending.gif > > > maven-1.1-beta-3 seems to corrupt images during a . > I'll attach two samples: > - corrupt-copy (2284 bytes) > - original (843 bytes) -- 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: (MAVEN-1692) improve error when 1.0.2 was in path but MAVEN_HOME is 1.1
[ http://jira.codehaus.org/browse/MAVEN-1692?page=all ] Arnaud Heritier updated MAVEN-1692: --- Fix Version/s: 1.1-rc1 > improve error when 1.0.2 was in path but MAVEN_HOME is 1.1 > -- > > Key: MAVEN-1692 > URL: http://jira.codehaus.org/browse/MAVEN-1692 > Project: Maven 1.x > Issue Type: Improvement >Reporter: Brett Porter > Fix For: 1.1-rc1 > > > currently, this errors out when trying to do XML things as the parser sys > properties are set. > At the start of the app, test the sys props, and if set, check they are > available. Give a helpful error message if not. -- 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: (MAVEN-1103) improve "goal not found" reporting
[ http://jira.codehaus.org/browse/MAVEN-1103?page=all ] Arnaud Heritier updated MAVEN-1103: --- Fix Version/s: 1.1-rc1 > improve "goal not found" reporting > -- > > Key: MAVEN-1103 > URL: http://jira.codehaus.org/browse/MAVEN-1103 > Project: Maven 1.x > Issue Type: Improvement > Components: core >Affects Versions: 1.0-rc1 >Reporter: Brett Porter >Priority: Minor > Fix For: 1.1-rc1 > > > - goal not found should be an error message, not an exception when leaving > maven > - goals that are not found should be reported before any building is done -- 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: (MAVEN-1459) misleading error message
[ http://jira.codehaus.org/browse/MAVEN-1459?page=all ] Arnaud Heritier updated MAVEN-1459: --- Fix Version/s: 1.1-rc1 > misleading error message > > > Key: MAVEN-1459 > URL: http://jira.codehaus.org/browse/MAVEN-1459 > Project: Maven 1.x > Issue Type: Improvement > Components: plugin manager >Reporter: Brett Porter > Fix For: 1.1-rc1 > > > > > > > run this inside reactor (notice missing goal). > error message is "nested plugin housings" -- 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: (MAVEN-1106) remove poor uses of system.err/out in core and plugins
[ http://jira.codehaus.org/browse/MAVEN-1106?page=all ] Arnaud Heritier updated MAVEN-1106: --- Fix Version/s: 1.1-rc1 > remove poor uses of system.err/out in core and plugins > -- > > Key: MAVEN-1106 > URL: http://jira.codehaus.org/browse/MAVEN-1106 > Project: Maven 1.x > Issue Type: Task >Affects Versions: 1.0-rc1 >Reporter: Brett Porter >Priority: Minor > Fix For: 1.1-rc1 > > > use logging mechanisms instead so destination of certain levels can be > controlled. -- 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-1016) group rename breaks security roles
[ http://jira.codehaus.org/browse/CONTINUUM-1016?page=all ] Jesse McConnell closed CONTINUUM-1016. -- Resolution: Fixed Fix Version/s: 1.1 fixed this finally issue was that dynamic roles were not getting renamed from top to bottom completely because the string name indices of jpox were silently _not_ updating despite the set operations we have on them > group rename breaks security roles > -- > > Key: CONTINUUM-1016 > URL: http://jira.codehaus.org/browse/CONTINUUM-1016 > Project: Continuum > Issue Type: Bug > Components: Web - Security >Affects Versions: 1.1 >Reporter: Jesse McConnell > Assigned To: Jesse McConnell > Fix For: 1.1 > > > When a group is renamed the corresponding dynamic roles are no longer linked > up correctly so authz fails for all subsequent checks > resolution is two parts: > a) validate on continuum startup that all groups have corresponding roles > created, and if missing then generate them > b) on group rename update the existing roles to reflect the change -- 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] Reopened: (CONTINUUM-1033) Unable to find text for key 'releaseProject.page.title' in ResourceBundles for locale 'en_US'
[ http://jira.codehaus.org/browse/CONTINUUM-1033?page=all ] Edwin Punzalan reopened CONTINUUM-1033: --- Sorry, but I seem to have missed some revisions in the patch... please apply the second patch too, thanks. > Unable to find text for key 'releaseProject.page.title' in ResourceBundles > for locale 'en_US' > - > > Key: CONTINUUM-1033 > URL: http://jira.codehaus.org/browse/CONTINUUM-1033 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Reporter: Edwin Punzalan > Assigned To: Carlos Sanchez > Fix For: 1.1 > > Attachments: CONTINUUM-1033-continuum-webapp.patch > > -- 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: (CONTINUUM-1033) Unable to find text for key 'releaseProject.page.title' in ResourceBundles for locale 'en_US'
[ http://jira.codehaus.org/browse/CONTINUUM-1033?page=all ] Edwin Punzalan updated CONTINUUM-1033: -- Attachment: CONTINUUM-1033-continuum-webapp-2.patch > Unable to find text for key 'releaseProject.page.title' in ResourceBundles > for locale 'en_US' > - > > Key: CONTINUUM-1033 > URL: http://jira.codehaus.org/browse/CONTINUUM-1033 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Reporter: Edwin Punzalan > Assigned To: Carlos Sanchez > Fix For: 1.1 > > Attachments: CONTINUUM-1033-continuum-webapp-2.patch, > CONTINUUM-1033-continuum-webapp.patch > > -- 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-1033) Unable to find text for key 'releaseProject.page.title' in ResourceBundles for locale 'en_US'
[ http://jira.codehaus.org/browse/CONTINUUM-1033?page=all ] Jesse McConnell closed CONTINUUM-1033. -- Assignee: Jesse McConnell (was: Carlos Sanchez) Resolution: Fixed applied, thanks edwin > Unable to find text for key 'releaseProject.page.title' in ResourceBundles > for locale 'en_US' > - > > Key: CONTINUUM-1033 > URL: http://jira.codehaus.org/browse/CONTINUUM-1033 > Project: Continuum > Issue Type: Bug > Components: Web - UI >Reporter: Edwin Punzalan > Assigned To: Jesse McConnell > Fix For: 1.1 > > Attachments: CONTINUUM-1033-continuum-webapp-2.patch, > CONTINUUM-1033-continuum-webapp.patch > > -- 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-787) xml tags are visible in rendered webpage
[ http://jira.codehaus.org/browse/CONTINUUM-787?page=all ] Jesse McConnell closed CONTINUUM-787. - Assignee: Jesse McConnell Resolution: Fixed applied, thanks much > xml tags are visible in rendered webpage > > > Key: CONTINUUM-787 > URL: http://jira.codehaus.org/browse/CONTINUUM-787 > Project: Continuum > Issue Type: Bug > Components: Documentation >Affects Versions: 1.1 > Environment: website >Reporter: Philippe Faes > Assigned To: Jesse McConnell >Priority: Trivial > Fix For: 1.1 > > Attachments: site-patch.txt > > > XML CDATA tag is visible in rendered webpage about.html. Patch is attached. -- 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: (MAVENUPLOAD-1267) Upload of novell jldap
Upload of novell jldap -- Key: MAVENUPLOAD-1267 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1267 Project: maven-upload-requests Issue Type: Task Reporter: Marc Boorshtein I am a commiter for the openldap project (which hosts the source for JLDAP). I can not find a commiter's list, but a search of openldap.org has several pages of results with my name. -- 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: (MAVENUPLOAD-1267) Upload of novell jldap
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1267?page=comments#action_82214 ] Carlos Sanchez commented on MAVENUPLOAD-1267: - where did you get the jar originally? being a binary from a commercial company i'd need to check throughly. > Upload of novell jldap > -- > > Key: MAVENUPLOAD-1267 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1267 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marc Boorshtein > > I am a commiter for the openldap project (which hosts the source for JLDAP). > I can not find a commiter's list, but a search of openldap.org has several > pages of results with my name. -- 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: (MAVENUPLOAD-1267) Upload of novell jldap
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1267?page=comments#action_82215 ] Marc Boorshtein commented on MAVENUPLOAD-1267: -- The jar is from novell's current download: http://developer.novell.com/wiki/index.php/Jldap The source is stored in the openldap.org CVS repository (referenced in the POM as well): http://www.openldap.org/jldap/ > Upload of novell jldap > -- > > Key: MAVENUPLOAD-1267 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1267 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marc Boorshtein > > I am a commiter for the openldap project (which hosts the source for JLDAP). > I can not find a commiter's list, but a search of openldap.org has several > pages of results with my name. -- 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: (MSUREFIRE-49) environmentVariables does not work with windows
[ http://jira.codehaus.org/browse/MSUREFIRE-49?page=comments#action_82218 ] Dan Tran commented on MSUREFIRE-49: --- latest plexus-utils snapshot does not exhibit this problem any more. Does it mean we need to get this new plexus-utils into maven-2.0.5 and release this plugin after that? > environmentVariables does not work with windows > --- > > Key: MSUREFIRE-49 > URL: http://jira.codehaus.org/browse/MSUREFIRE-49 > Project: Maven 2.x Surefire Plugin > Issue Type: Bug >Affects Versions: 2.1.2 > Environment: windows >Reporter: Dan Tran > Fix For: 2.3 > > Attachments: MSUREFIRE-49.log > > > MSUREFIRE-44 added environmentVariables fields to all additional environment > variables to be added to when forking the test > It works on UNIX but not windows. Suspect it is platform specific problem > for windows in plexus-util's cli library > Here is the plugin configuration to reproduce the problem > >maven-surefire-plugin > > >value > > once > > > and the stack trace is > > [[DEBUG] Adding to surefire test classpath: > c:\dev\maven\maven-2.0.2\core\plexus- > utils-1.1.jar > Environment: key=value added. > java -classpath "C:\Documents and > Settings\dtran\.m2\repository\org\apache\maven > \surefire\surefire-booter\1.5.3-SNAPSHOT\surefire-booter-1.5.3-SNAPSHOT.jar;c:\d > ev\maven\maven-2.0.2\core\plexus-utils-1.1.jar" > org.apache.maven.surefire.Surefi > reBooter C:\dev\maven\src\surefire\surefire > [INFO] > - > --- > [ERROR] BUILD ERROR > [INFO] > - > --- > [INFO] There are some test failure. > [INFO] > - > --- > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: There are some test > fail > ure. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:472) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:303) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:270) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:139) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > 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) > Caused by: org.apache.maven.plugin.MojoExecutionException: There are some > test f > ailure. > at > org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:404) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:415) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:531) > ... 16 more > [INFO] > - > --- > [INFO] Total time: 4 seconds > [INFO] Finished at: Sat Jan 21 10:18:59 PST 2006 > [INFO] Final Memory: 3M/6M > [INFO] > - > --- -- 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
