[jira] Commented: (MNG-2477) Implement repository security improvements for verification of downloaded artifacts
[ http://jira.codehaus.org/browse/MNG-2477?page=comments#action_78009 ] Brett Porter commented on MNG-2477: --- one thought on a quicker gpg implementation: fork gpg (assume it exists, handle the exception if not or disable the capability), and then attach the resulting .aasc to an upload. This won't handle downloads but at least gets us the deployment functionality that is highly requested > Implement repository security improvements for verification of downloaded > artifacts > --- > > Key: MNG-2477 > URL: http://jira.codehaus.org/browse/MNG-2477 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Design, Patterns & Best > Practices, Dependencies, Deployment, Repositories, Artifacts >Reporter: Brett Porter > > http://docs.codehaus.org/display/MAVEN/Repository+Security+Improvements -- 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-1577) dependencyManagement does not work for transitive dependencies
[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_78005 ] Ralph Goers commented on MNG-1577: -- Thanks for the feedback. I'll see if I can address these problems. Did you happen to create test cases that I can use? > dependencyManagement does not work for transitive dependencies > -- > > Key: MNG-1577 > URL: http://jira.codehaus.org/browse/MNG-1577 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0 >Reporter: Joerg Schaible > Fix For: 2.1 > > Attachments: mng1577.patch, mng1577a.patch, mng1577b.patch, > mng1577trunk.patch > > > The dependencyManagement does not work for transient dependencies. The > specified version is ignored. > Use case: > Main POM defines commons-digester-1.6 and commons-beanutils-1.7.0, A-SNAPSHOT > and B-SNAPSHOT > Project A is child of Main and depends directly on commons-beanutils (version > inherited from Main) > Project B is child of Main and depends directly on commons-digester (version > inherited from Main) > Project C is child of Main and depends directly on A & B (versions inherited > from Main) > A is compiled and tests are run using commons-beanutils-1.7.0 > B is compiled and tests are run using commons-digester-1.6 and > commons-beanutils-1.6, since digester is dependend on this > C is compiled and tests are run using commons-beanutils-1.7.0 > Integration tests of B did not verify, that B is behaving as expected in this > scenario. B might fail with 1.7.0 and it is not even recognized. > If I add beanutils also as direct dependency to B, it works fine, but then > are transitive dependency useless. It should be possible to define at least > in the dependencyManagement, that the versions of transient dependencies also > defined in the dependencyManagement have priority. > - Jörg -- 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-1191) Upload AjaxAnywhere 1.2-rc2
Upload AjaxAnywhere 1.2-rc2 --- Key: MAVENUPLOAD-1191 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1191 Project: maven-upload-requests Issue Type: Wish Reporter: Matt Raible -- 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: (MPMD-47) pmd should support multiple source roots
pmd should support multiple source roots Key: MPMD-47 URL: http://jira.codehaus.org/browse/MPMD-47 Project: Maven 2.x Pmd Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Brian Fox pmd and cpd don't read the source roots to find other locations for source to check. -- 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: (MPMD-43) Add results output to pmd:check
[ http://jira.codehaus.org/browse/MPMD-43?page=all ] Brian Fox updated MPMD-43: -- Fix Version/s: 2.2 pmd:check is done. cpd:check needs to be completed. > Add results output to pmd:check > --- > > Key: MPMD-43 > URL: http://jira.codehaus.org/browse/MPMD-43 > Project: Maven 2.x Pmd Plugin > Issue Type: New Feature >Affects Versions: 2.1 >Reporter: Brian Fox > Assigned To: Brian Fox > Fix For: 2.2 > > > We need the ability to have the results printed to the build output when the > pmd:check fails the build. This should be an optional flag defaulted to > false. This should be something similar to the checkstyle output. The main > reason is simplicity for a developer to see why a build failed, but also so > we can see the problem in continuum build failures without having to go find > the pmd.xml file. -- 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-734) Can't use continuum behind https proxy
[ http://jira.codehaus.org/browse/CONTINUUM-734?page=all ]
Brian Fox updated CONTINUUM-734:
Attachment: mod_proxy_http.so
I was able to work around this using the http proxy reverse. This scans
outbound html and replaces urls. The standard mod_proxy only scans the headers
so it won't correct embedded links.
Attached prebuilt module for Windows/Apache 2.0.55. The source can be obtained
here:http://apache.webthing.com/mod_proxy_html/
I added this file to the 2.0.55 mod_proxy_http module and rebuilt so this can
replace the standard mod_proxy_http.so
In the config below, i redirect /continum to another machine mapped to /ts.
Then I have the htmlurl map set to look for the url that continuum will return
in its links and map it back to /ts.
RedirectMatch /continuum /ts/continuum/servlet/continuum
ProxyRequests off
ProxyPass /ts/ http://10.0.5.251:8080/
ProxyHTMLURLMap http://continum-machine:8080 /ts
ProxyHTMLURLMap http://10.0.5.251:8080 /ts
ProxyPassReverse /
SetOutputFilter proxy-html
ProxyHTMLURLMap / /ts/
ProxyHTMLURLMap /ts/ts
RequestHeaderunset Accept-Encoding
> Can't use continuum behind https proxy
> --
>
> Key: CONTINUUM-734
> URL: http://jira.codehaus.org/browse/CONTINUUM-734
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
>Affects Versions: 1.0.3
>Reporter: Richard van der Hoff
> Fix For: 1.1
>
> Attachments: mod_proxy_http.so
>
>
> As noted in CONTINUUM-240, it's not currentlyy possible to run the continuum
> webapp behind an https proxy, as all the links are http://...
> My apache setup is something along the lines of:
> {code:xml}
>
> SSLEngine on
> ProxyPass / http://localhost:8080/
> ProxyPassReverse / http://localhost:8080/
> ProxyPreserveHost On
>
> {code}
> and my jetty config:
> {code:xml}
>
>
> 8080
>
>
> {code}
> The links are correct, except that they have s/https/http/.
> Why does the webapp need to use absolute links anyway?
--
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-1577) dependencyManagement does not work for transitive dependencies
[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_77990 ]
Mike Perham commented on MNG-1577:
--
I changed this in
src/main/java/org/apache/maven/artifact/resolver/DefaultArtifactCollector.java
-if ( artifact.getScope() != null )
+if ( artifact.getScope() != null && node.getArtifact().getScope()
== null )
{
node.getArtifact().setScope( artifact.getScope() );
This fixed my problem above but it still does not work properly with transitive
dependencies that are marked as optional. They become non-optional if listed
in the dependency management section.
A transitive dep has it marked as compile/optional whereas my depMgmt section
has it marked as test/non-optional. At runtime this becomes
compile/non-optional and gets included in my EAR.
Also when I turn on true, my EAR build goes from 8 seconds
to 40 seconds and my -X output goes from 170k to 9MB. I believe this is
because it is parsing the same deps over and over, without caching intermediate
results.
IOW, this patch needs more work.
> dependencyManagement does not work for transitive dependencies
> --
>
> Key: MNG-1577
> URL: http://jira.codehaus.org/browse/MNG-1577
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 2.0
>Reporter: Joerg Schaible
> Fix For: 2.1
>
> Attachments: mng1577.patch, mng1577a.patch, mng1577b.patch,
> mng1577trunk.patch
>
>
> The dependencyManagement does not work for transient dependencies. The
> specified version is ignored.
> Use case:
> Main POM defines commons-digester-1.6 and commons-beanutils-1.7.0, A-SNAPSHOT
> and B-SNAPSHOT
> Project A is child of Main and depends directly on commons-beanutils (version
> inherited from Main)
> Project B is child of Main and depends directly on commons-digester (version
> inherited from Main)
> Project C is child of Main and depends directly on A & B (versions inherited
> from Main)
> A is compiled and tests are run using commons-beanutils-1.7.0
> B is compiled and tests are run using commons-digester-1.6 and
> commons-beanutils-1.6, since digester is dependend on this
> C is compiled and tests are run using commons-beanutils-1.7.0
> Integration tests of B did not verify, that B is behaving as expected in this
> scenario. B might fail with 1.7.0 and it is not even recognized.
> If I add beanutils also as direct dependency to B, it works fine, but then
> are transitive dependency useless. It should be possible to define at least
> in the dependencyManagement, that the versions of transient dependencies also
> defined in the dependencyManagement have priority.
> - Jörg
--
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: (WAGONSSH-53) Error deploying artifact: Authentication failed: Cannot connect. Reason:
[ http://jira.codehaus.org/browse/WAGONSSH-53?page=all ] Brett Porter closed WAGONSSH-53. Resolution: Duplicate it's a bug in the release you are using. You can either: a) mkdir ~/.ssh, then run interactive once (from then on, non interactive will work) b) ssh to the host using the command line ssh, answer yes so that known_hosts is created > Error deploying artifact: Authentication failed: Cannot connect. Reason: > - > > Key: WAGONSSH-53 > URL: http://jira.codehaus.org/browse/WAGONSSH-53 > Project: wagon-ssh > Issue Type: Bug > Environment: My operating system is unix > sun4-cross: uname -a > SunOS swdc-sf06e 5.8 Generic_117350-24 sun4u sparc SUNW,Sun-Fire-15000 >Reporter: sharda sheshabhattar > > Hi, > I am having problems using Maven deploy feature in the non interactive mode. > However the same command ,when used in the interactive mode works fine. It > prompts me for > The authenticity of host 'dsddb2d-swdc' can't be established. > DSA key fingerprint is 09:a4:e9:e9:44:2e:59:d0:91:40:09:47:32:91:39:be. > Are you sure you want to continue connecting? (yes/no): > It proceeds when I type yes.It prompts me about 4-5 times for each deploy. > I need to urgently develop something and make this work in the > non-interactive mode. Please help > Regards, > Sharda > Here is the trace output when I run in the non-interactive mode: > > /xenv/Maven/X/2.0.4/bin/mvn -s settings.xml deploy:deploy-file > -DpomFile=commons-digester-1.5.pom -Dr > epositoryId=nyhub1 -Durl=scp://nyhub1/xenv/scripts/Hermesmvnrep > -Dfile=/xenv/commons-digester/X/1.5/l > ib/commons-digester.jar > + Error stacktraces are turned on. > Maven version: 2.0.4 > [DEBUG] Building Maven user-level plugin registry from: > '/home/sunle/.m2/plugin-registry.xml' > [DEBUG] Building Maven global-level plugin registry from: > '/xenv/Maven/X/2.0.4/conf/plugin-registry.x > ml' > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'deploy'. > [DEBUG] maven-deploy-plugin: resolved to version 2.2.1 from repository central > [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for > project: null:maven-depl > oy-plugin:maven-plugin:2.2.1 from the repository. > [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: > org.apache.maven.plugins > :maven-plugins:pom:1 from the repository. > [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: > org.apache.maven:maven-parent:pom:1 > from the repository. > [INFO] > > [INFO] Building Maven Default Project > [INFO]task-segment: [deploy:deploy-file] (aggregator-style) > [INFO] > > [DEBUG] > org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:2.2.1:runtime > (selected for runtime > ) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apache.maven:maven-artifa > ct-manager:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime (selected > for runtime) > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for > runtime) > [DEBUG] > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime > (selected for runtim > e) > [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for > runtime) > [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apache.maven:maven-artifa > ct:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for > runtime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apache.maven:maven-reposi > tory-metadata:jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime > (selected for runtime) > [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime > (selected for runtime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-project:jar:2.0 fr > om the repository. > [DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for > runtime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > org.apache.maven:maven-model: > jar:2.0 from the repository. > [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for > runtime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: > null:maven-profile:jar:2.0 fr > om the repository. > [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for > runtime) > [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: >
[jira] Created: (MPMD-46) Add ability to choose priority for failure
Add ability to choose priority for failure -- Key: MPMD-46 URL: http://jira.codehaus.org/browse/MPMD-46 Project: Maven 2.x Pmd Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Brian Fox Assigned To: Brian Fox Need to add the ability to run the rules but only fail above a certain priority level. -- 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-124) Impossible to depend on a deployed snapshot
[ http://jira.codehaus.org/browse/MRELEASE-124?page=comments#action_77982 ] Brian Topping commented on MRELEASE-124: I should add this patch is against revision 465377. > Impossible to depend on a deployed snapshot > --- > > Key: MRELEASE-124 > URL: http://jira.codehaus.org/browse/MRELEASE-124 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-4 >Reporter: Mike Perham >Priority: Critical > Attachments: releasePluginIgnoreSnapshot.patch > > > I have a SNAPSHOT of the war plugin that I built and deployed to fix a > blocker for us (MWAR-39) that has not been released. In my POM, I refer to > it like this: > > > > maven-war-plugin > 2.0.1-20060525.222101-1 > I did this specifically so the release plugin would not think it was a > SNAPSHOT so I could release the module. But when I do try to release, I get > this error: > [INFO] Can't release project due to non released dependencies : > > org.apache.maven.plugins:maven-war-plugin:maven-plugin:2.0.1-SNAPSHOT:runtime > in project 'UDDI WAR' (com.webify.fabric:fabric-uddi-web:war:1.1.0-SNAPSHOT) > This is because in ArtifactUtils.isSnapshot, it specifically disallows the > version pattern created by the deploy plugin. > So consider my usecase: I'm Joe Corporate, a user who needs a war bug fix in > their build process ASAP. I build and deploy the latest war plugin to my > internal repo and reference that explicit timestamp version in my build > process. Now I can understand why you disallow this because if I try to > build outside of our corporate walls, it will not work. But I can't use the > release plugin to release either because it requires me to check the modified > POMs into my SCM and the war plugin is in Apache's SCM and I can't check into > it. > There's only two hack workarounds I can think of: 1) explicitly reversion the > jar to not include SNAPSHOT or the specific timestamp pattern. 2) Check the > war plugin into our own SCM and release from there, effectively forking the > code. > Your thoughts? How can we fix bugs in the build process locally and still > use the release plugin? -- 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-1577) dependencyManagement does not work for transitive dependencies
[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_77979 ] Mike Perham commented on MNG-1577: -- -1 on this patch as is. If I have a dep in the child POM: junit junit compile and a dep in depMgmt in the parent POM: junit junit 3.8.1 test It forces the dep to the 'test' scope despite the fact that the child requires it as compile. The child should *always* override everything else. WYSIWYG. > dependencyManagement does not work for transitive dependencies > -- > > Key: MNG-1577 > URL: http://jira.codehaus.org/browse/MNG-1577 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0 >Reporter: Joerg Schaible > Fix For: 2.1 > > Attachments: mng1577.patch, mng1577a.patch, mng1577b.patch, > mng1577trunk.patch > > > The dependencyManagement does not work for transient dependencies. The > specified version is ignored. > Use case: > Main POM defines commons-digester-1.6 and commons-beanutils-1.7.0, A-SNAPSHOT > and B-SNAPSHOT > Project A is child of Main and depends directly on commons-beanutils (version > inherited from Main) > Project B is child of Main and depends directly on commons-digester (version > inherited from Main) > Project C is child of Main and depends directly on A & B (versions inherited > from Main) > A is compiled and tests are run using commons-beanutils-1.7.0 > B is compiled and tests are run using commons-digester-1.6 and > commons-beanutils-1.6, since digester is dependend on this > C is compiled and tests are run using commons-beanutils-1.7.0 > Integration tests of B did not verify, that B is behaving as expected in this > scenario. B might fail with 1.7.0 and it is not even recognized. > If I add beanutils also as direct dependency to B, it works fine, but then > are transitive dependency useless. It should be possible to define at least > in the dependencyManagement, that the versions of transient dependencies also > defined in the dependencyManagement have priority. > - Jörg -- 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-1190) Upload Struts Menu 2.4.2
Upload Struts Menu 2.4.2 Key: MAVENUPLOAD-1190 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1190 Project: maven-upload-requests Issue Type: Wish Reporter: Matt Raible -- 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: (WAGONSSH-53) Error deploying artifact: Authentication failed: Cannot connect. Reason:
Error deploying artifact: Authentication failed: Cannot connect. Reason: - Key: WAGONSSH-53 URL: http://jira.codehaus.org/browse/WAGONSSH-53 Project: wagon-ssh Issue Type: Bug Environment: My operating system is unix sun4-cross: uname -a SunOS swdc-sf06e 5.8 Generic_117350-24 sun4u sparc SUNW,Sun-Fire-15000 Reporter: sharda sheshabhattar Hi, I am having problems using Maven deploy feature in the non interactive mode. However the same command ,when used in the interactive mode works fine. It prompts me for The authenticity of host 'dsddb2d-swdc' can't be established. DSA key fingerprint is 09:a4:e9:e9:44:2e:59:d0:91:40:09:47:32:91:39:be. Are you sure you want to continue connecting? (yes/no): It proceeds when I type yes.It prompts me about 4-5 times for each deploy. I need to urgently develop something and make this work in the non-interactive mode. Please help Regards, Sharda Here is the trace output when I run in the non-interactive mode: /xenv/Maven/X/2.0.4/bin/mvn -s settings.xml deploy:deploy-file -DpomFile=commons-digester-1.5.pom -Dr epositoryId=nyhub1 -Durl=scp://nyhub1/xenv/scripts/Hermesmvnrep -Dfile=/xenv/commons-digester/X/1.5/l ib/commons-digester.jar + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/home/sunle/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/xenv/Maven/X/2.0.4/conf/plugin-registry.x ml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'deploy'. [DEBUG] maven-deploy-plugin: resolved to version 2.2.1 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-depl oy-plugin:maven-plugin:2.2.1 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins :maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [deploy:deploy-file] (aggregator-style) [INFO] [DEBUG] org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:2.2.1:runtime (selected for runtime ) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-artifa ct-manager:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime (selected for runtim e) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for runtime) [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-artifa ct:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-reposi tory-metadata:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime (selected for runtime) [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-project:jar:2.0 fr om the repository. [DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-model: jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-profile:jar:2.0 fr om the repository. [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: org.apache.maven:maven-core:j ar:2.0 from the repository. [DEBUG] org.apache.maven:maven-core:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-plugin-parameter-d ocumenter:jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-plugin-parameter-documenter:jar:2.0:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0 for project: null:maven-error-diagnostics: jar:2.0 from the repository. [DEBUG] org.apache.maven:maven-error-diagnostics:jar:2.0:runtime (select
[jira] Closed: (CONTINUUM-963) Derby Database initialization error on Webapp restarts on Jetty
[ http://jira.codehaus.org/browse/CONTINUUM-963?page=all ] Jesse McConnell closed CONTINUUM-963. - Assignee: Jesse McConnell Resolution: Fixed Fix Version/s: 1.1 updated the version of that, thanks > Derby Database initialization error on Webapp restarts on Jetty > > > Key: CONTINUUM-963 > URL: http://jira.codehaus.org/browse/CONTINUUM-963 > Project: Continuum > Issue Type: Bug >Reporter: Rahul Thakur > Assigned To: Jesse McConnell > Fix For: 1.1 > > Attachments: CONTINUUM-963.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] Commented: (CONTINUUM-734) Can't use continuum behind https proxy
[ http://jira.codehaus.org/browse/CONTINUUM-734?page=comments#action_77958
]
Carlos Sanchez commented on CONTINUUM-734:
--
I think this is already fixed for 1.1
> Can't use continuum behind https proxy
> --
>
> Key: CONTINUUM-734
> URL: http://jira.codehaus.org/browse/CONTINUUM-734
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
>Affects Versions: 1.0.3
>Reporter: Richard van der Hoff
> Fix For: 1.1
>
>
> As noted in CONTINUUM-240, it's not currentlyy possible to run the continuum
> webapp behind an https proxy, as all the links are http://...
> My apache setup is something along the lines of:
> {code:xml}
>
> SSLEngine on
> ProxyPass / http://localhost:8080/
> ProxyPassReverse / http://localhost:8080/
> ProxyPreserveHost On
>
> {code}
> and my jetty config:
> {code:xml}
>
>
> 8080
>
>
> {code}
> The links are correct, except that they have s/https/http/.
> Why does the webapp need to use absolute links anyway?
--
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-962) Clean up CSS styles for validation/error messages
[ http://jira.codehaus.org/browse/CONTINUUM-962?page=all ] Jesse McConnell updated CONTINUUM-962: -- Affects Version/s: 1.1 Fix Version/s: 1.1 > Clean up CSS styles for validation/error messages > - > > Key: CONTINUUM-962 > URL: http://jira.codehaus.org/browse/CONTINUUM-962 > Project: Continuum > Issue Type: Task > Components: Web interface >Affects Versions: 1.1 >Reporter: Rahul Thakur > Assigned To: Jesse McConnell > Fix For: 1.1 > > Attachments: CONTINUUM-962.patch, > CONTINUUM-962_new_postsubmit_form.jpg, > CONTINUUM-962_new_unsubmitted_form.jpg, > CONTINUUM-962_original_postsubmit_form.jpg, > CONTINUUM-962_original_unsubmitted_form.jpg > > -- 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-962) Clean up CSS styles for validation/error messages
[ http://jira.codehaus.org/browse/CONTINUUM-962?page=all ] Jesse McConnell closed CONTINUUM-962. - Resolution: Fixed applied, thanks rahul > Clean up CSS styles for validation/error messages > - > > Key: CONTINUUM-962 > URL: http://jira.codehaus.org/browse/CONTINUUM-962 > Project: Continuum > Issue Type: Task > Components: Web interface >Reporter: Rahul Thakur > Assigned To: Jesse McConnell > Attachments: CONTINUUM-962.patch, > CONTINUUM-962_new_postsubmit_form.jpg, > CONTINUUM-962_new_unsubmitted_form.jpg, > CONTINUUM-962_original_postsubmit_form.jpg, > CONTINUUM-962_original_unsubmitted_form.jpg > > -- 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-1150) Java2html 5.0 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1150?page=comments#action_77939 ] Guilherme Silveira commented on MAVENUPLOAD-1150: - Sorry Carlos... typo on the url bundle. Its the 5.0 release (as stated in the title): http://www.vraptor.org/java2html-5.0-bundle.jar By the way, this is not the same project contained under java2html/j2h at ibiblio. > Java2html 5.0 upload > > > Key: MAVENUPLOAD-1150 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1150 > Project: maven-upload-requests > Issue Type: Task >Reporter: Guilherme Silveira > > Java2html is a tool that generates html code from java source, with various > styles and so on. > I am not a team member and could not find the scm location anywhere on the > site. I am opening this issue just missing the scm location in order to check > it its possible. > Its sourcecode is included with the complete download on their page. -- 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: (MRM-211) Cannot use Archiva to get Maven1 Plugins
[ http://jira.codehaus.org/browse/MRM-211?page=comments#action_77937 ] nicolas de loof commented on MRM-211: - Seems to be duplicated fomr MRM-210 > Cannot use Archiva to get Maven1 Plugins > > > Key: MRM-211 > URL: http://jira.codehaus.org/browse/MRM-211 > Project: Archiva > Issue Type: Bug > Components: remote proxy >Reporter: nicolas de loof >Priority: Minor > > I request maven PMD plugin 1.9 using maven1 > Archiva looks into http://repo1.maven.org/maven2/maven/maven-pmd-plugin/1.9/ > and get the POM -> OK > It then searchs the Artifact as > "maven/maven-pmd-plugin/1.9/maven-pmd-plugin-1.9.plugin" -> NOK > Even looking at maven/maven-pmd-plugin/1.9/maven-pmd-plugin-1.9.jar fails : > the artifact doesn't exist ! It has a POM and a sources-jar but no binary > artifact. Maybe a m1-to-m2 repo-converter error ? -- 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: (MNGECLIPSE-204) JAR dependencies ignored
JAR dependencies ignored - Key: MNGECLIPSE-204 URL: http://jira.codehaus.org/browse/MNGECLIPSE-204 Project: Maven 2.x Extension for Eclipse Issue Type: Bug Components: Dependency Resolver Affects Versions: 0.0.9 Reporter: Al Maw I depend on the tests in one project in another, where I extend them. If the artifact is not available as another project managed using the plug-in, the plug-in fails to add the foo-x.y-tests.jar to the classpath container. To publish the test artifact: maven-jar-plugin test-jar To include the artifact in another project: tests test If you find this hard to reproduce/fathom and require a test case, please add a comment and I can cook one up for you. -- 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: (CONTINUUM-964) Perforce integration doesn't remove deleted files from working directory
Perforce integration doesn't remove deleted files from working directory Key: CONTINUUM-964 URL: http://jira.codehaus.org/browse/CONTINUUM-964 Project: Continuum Issue Type: Bug Components: SCM Environment: > uname -a Linux cod 2.6.17-2-686 #1 SMP Wed Sep 13 16:34:10 UTC 2006 i686 GNU/Linux > java -version java version "1.4.2_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04) Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode) Reporter: Michael Stevens I'm using continuum to build projects from a perforce scm servers. When files are deleted in perforce, they are not deleted in the continuum working directory. This tends to quickly lead to build failures as the now obsolete files stop compiling. -- 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: (MRM-211) Cannot use Archiva to get Maven1 Plugins
Cannot use Archiva to get Maven1 Plugins Key: MRM-211 URL: http://jira.codehaus.org/browse/MRM-211 Project: Archiva Issue Type: Bug Components: remote proxy Reporter: nicolas de loof Priority: Minor I request maven PMD plugin 1.9 using maven1 Archiva looks into http://repo1.maven.org/maven2/maven/maven-pmd-plugin/1.9/ and get the POM -> OK It then searchs the Artifact as "maven/maven-pmd-plugin/1.9/maven-pmd-plugin-1.9.plugin" -> NOK Even looking at maven/maven-pmd-plugin/1.9/maven-pmd-plugin-1.9.jar fails : the artifact doesn't exist ! It has a POM and a sources-jar but no binary artifact. Maybe a m1-to-m2 repo-converter error ? -- 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: (MCHECKSTYLE-47) Allow running checkstyle in test sources
[ http://jira.codehaus.org/browse/MCHECKSTYLE-47?page=all ] Vincent Siveton closed MCHECKSTYLE-47. -- Assignee: Vincent Siveton Resolution: Fixed Fixed with a new plugin parameter: includeTestSourceDirectory > Allow running checkstyle in test sources > > > Key: MCHECKSTYLE-47 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-47 > Project: Maven 2.x Checkstyle Plugin > Issue Type: New Feature >Affects Versions: 2.1 >Reporter: Carlos Sanchez > Assigned To: Vincent Siveton > Fix For: 2.2 > > > I think this is already implemented in maven 1 -- 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-1187) javassist 3.3.ga
javassist 3.3.ga Key: MAVENUPLOAD-1187 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1187 Project: maven-upload-requests Issue Type: Task Reporter: Mark Hobson javassist 3.3.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] Created: (MAVENUPLOAD-1188) jboss-archive-browsing 5.0.0alpha-200607201-119
jboss-archive-browsing 5.0.0alpha-200607201-119 --- Key: MAVENUPLOAD-1188 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1188 Project: maven-upload-requests Issue Type: Task Reporter: Mark Hobson jboss-archive-browsing 5.0.0alpha-200607201-119 As required by and specified in hibernate-entitymanager 3.2.0.ga: "jboss-archive-browsing (5.0.0alpha build: CVSTag=HEAD date=200607201 119)" Can't find a decent project URL for this one, any ideas welcome.. -- 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-1186) hibernate-tools 3.2.0.beta8
hibernate-tools 3.2.0.beta8 --- Key: MAVENUPLOAD-1186 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1186 Project: maven-upload-requests Issue Type: Task Reporter: Mark Hobson hibernate-tools 3.2.0.beta8 -- 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-1189) hibernate-entitymanager 3.2.0.ga
hibernate-entitymanager 3.2.0.ga Key: MAVENUPLOAD-1189 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1189 Project: maven-upload-requests Issue Type: Task Reporter: Mark Hobson hibernate-entitymanager 3.2.0.ga Depends on MAVENUPLOAD-1187 and MAVENUPLOAD-1188, along with the other hibernate 3.2.0.ga upload requests. -- 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-1185) hibernate-annotations 3.2.0.ga
hibernate-annotations 3.2.0.ga -- Key: MAVENUPLOAD-1185 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1185 Project: maven-upload-requests Issue Type: Task Reporter: Mark Hobson hibernate-annotations 3.2.0.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] Created: (MAVENUPLOAD-1184) hibernate 3.2.0.ga
hibernate 3.2.0.ga -- Key: MAVENUPLOAD-1184 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1184 Project: maven-upload-requests Issue Type: Task Reporter: Mark Hobson hibernate 3.2.0.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] Created: (MECLIPSE-177) While the plugin builds, the console cannot be shut down
While the plugin builds, the console cannot be shut down Key: MECLIPSE-177 URL: http://jira.codehaus.org/browse/MECLIPSE-177 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.3 Reporter: Aaron Digulla While the m2 plugin for eclipse is building, it will continously pop the console to the front. This makes it impossible to use the synchonize view, for example. Changing the console prefs (in run/debug - console) doesn't fix this. -- 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: (MWAR-9) WAR plugin should support minimal WARs for inclusion within an EAR
[ http://jira.codehaus.org/browse/MWAR-9?page=comments#action_77928 ] M. van Leeuwen commented on MWAR-9: --- Is adding a new scope not the easiest way? Just configure the dependency with scope 'ear' and it will not be included as jar in the WAR, but in the EAR. The plugin should without any configuration find these scoped dependencies and add them as a classpath entry to the manifest. > WAR plugin should support minimal WARs for inclusion within an EAR > -- > > Key: MWAR-9 > URL: http://jira.codehaus.org/browse/MWAR-9 > Project: Maven 2.x War Plugin > Issue Type: Improvement >Reporter: Mike Perham > > I noticed that when I build a WAR, I get a gigantic WEB-INF/lib with all my > deps. This is fine for a default but maven should also support "skeleton" > WARs which will be packaged within an EAR. We have EARs which package 3-4 > WARs each and to have the deps duplicated within each WAR means we cannot > have shared data (since the classes are loaded within each WAR's classloader, > rather than by the parent EAR's classloader). It also means 80MB EARs! :-) > It seems like two things need to happen: > 1) Add a "skeleton" flag which prevents copying any dependencies to > WEB-INF/lib. > 2) Instead generate a META-INF/MANIFEST.MF which has a Class-Path entry which > lists the relative locations of the dependencies within the parent EAR. > Fabrice has basically the same idea written down here. Starting with "- for > a War..." : > http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112737860024530&w=2 -- 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: (MCHECKSTYLE-51) Rules summary flexibility:add possibility to hide non-violated rules and to sort by descending number of occurences
[ http://jira.codehaus.org/browse/MCHECKSTYLE-51?page=comments#action_77927 ] Vincent Siveton commented on MCHECKSTYLE-51: Olivier, Thanks! Your patch sounds good (for the next time, please ensure you use our checkstyle [1]). Could you provide us: * small documentation (ie one example) [2] * unit tests with plugin harness [3] Thanks again. [1] http://maven.apache.org/guides/development/guide-m2-development.html#Maven%20Code%20Style [2] http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Documentation [3] http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Harness > Rules summary flexibility:add possibility to hide non-violated rules and to > sort by descending number of occurences > --- > > Key: MCHECKSTYLE-51 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-51 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.1 > Environment: NA >Reporter: Olivier Vierlinck >Priority: Minor > Attachments: MNG-39787-maven-plugin-checkstyle.patch > > > While using maven + Checkstyle on a new project, the amount of > errors/warnings was quite high, due both because checkstyle was not yet > configured to match our preferences.. and also to real style errors. > To refine this, it very useful to tackle first the big problems=the one > occuring often > Similarly, it is helpful NOT to see the rules that are not violated, so that > we can concentrate on the existing problems -- 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: (MCHECKSTYLE-55) Wrong rules summary for GenericIllegalRegexp when message contains a quote
[ http://jira.codehaus.org/browse/MCHECKSTYLE-55?page=all ] Vincent Siveton closed MCHECKSTYLE-55. -- Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.2 Fixed. Remove single quote in msg due to java.text.MessageFormat specification. > Wrong rules summary for GenericIllegalRegexp when message contains a quote > -- > > Key: MCHECKSTYLE-55 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-55 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Windows XP - Maven 2.0.4 >Reporter: Olivier Vierlinck > Assigned To: Vincent Siveton >Priority: Minor > Fix For: 2.2 > > Attachments: MavenCheckstyleReportBug.zip > > > if a GenericIllegalRegexp check is defined and its 'message' property > contains a quote, the check is executed ok and failures are listed in the > Details part of the HTML report. > But the Rules summary part is wrong: it show the rules with 0 violations. > For example, this check > >name="message" value="Don't do this" /> > > will no be reported as violated in the rules summary (but the message text is > show correctly) > But will be listed in the errors on the file (but with the quote removed from > the message ;-) ) > See checkstyle.xml and target/site/checkstyle.html in attachment (and sample > code in src\main\java\MCTest\App.java) -- 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: (MCHECKSTYLE-58) Tests fail on non-English JVM
[ http://jira.codehaus.org/browse/MCHECKSTYLE-58?page=all ] Vincent Siveton closed MCHECKSTYLE-58. -- Resolution: Fixed Fixed > Tests fail on non-English JVM > - > > Key: MCHECKSTYLE-58 > URL: http://jira.codehaus.org/browse/MCHECKSTYLE-58 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Vincent Siveton > Assigned To: Vincent Siveton > Fix For: 2.2 > > > CheckstyleReportTest hardcodes English messages in tests. We need to set > English as default Locale. -- 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: (MCHECKSTYLE-58) Tests fail on non-English JVM
Tests fail on non-English JVM - Key: MCHECKSTYLE-58 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-58 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Vincent Siveton Assigned To: Vincent Siveton Fix For: 2.2 CheckstyleReportTest hardcodes English messages in tests. We need to set English as default Locale. -- 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: (CONTINUUM-962) Clean up CSS styles for validation/error messages
[ http://jira.codehaus.org/browse/CONTINUUM-962?page=comments#action_77924 ] Rahul Thakur commented on CONTINUUM-962: Note that the validation messages in new version also color the input field borders in red - this might not show up distinctly in screenshots > Clean up CSS styles for validation/error messages > - > > Key: CONTINUUM-962 > URL: http://jira.codehaus.org/browse/CONTINUUM-962 > Project: Continuum > Issue Type: Task > Components: Web interface >Reporter: Rahul Thakur > Attachments: CONTINUUM-962.patch, > CONTINUUM-962_new_postsubmit_form.jpg, > CONTINUUM-962_new_unsubmitted_form.jpg, > CONTINUUM-962_original_postsubmit_form.jpg, > CONTINUUM-962_original_unsubmitted_form.jpg > > -- 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-962) Clean up CSS styles for validation/error messages
[ http://jira.codehaus.org/browse/CONTINUUM-962?page=all ] Rahul Thakur updated CONTINUUM-962: --- Attachment: CONTINUUM-962_original_unsubmitted_form.jpg Original: Create Admin User Form (unsubmitted) > Clean up CSS styles for validation/error messages > - > > Key: CONTINUUM-962 > URL: http://jira.codehaus.org/browse/CONTINUUM-962 > Project: Continuum > Issue Type: Task > Components: Web interface >Reporter: Rahul Thakur > Attachments: CONTINUUM-962.patch, > CONTINUUM-962_new_postsubmit_form.jpg, > CONTINUUM-962_new_unsubmitted_form.jpg, > CONTINUUM-962_original_postsubmit_form.jpg, > CONTINUUM-962_original_unsubmitted_form.jpg > > -- 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-962) Clean up CSS styles for validation/error messages
[ http://jira.codehaus.org/browse/CONTINUUM-962?page=all ] Rahul Thakur updated CONTINUUM-962: --- Attachment: CONTINUUM-962_original_postsubmit_form.jpg Origina: Create Admin User form (post submit with validation/error messages) > Clean up CSS styles for validation/error messages > - > > Key: CONTINUUM-962 > URL: http://jira.codehaus.org/browse/CONTINUUM-962 > Project: Continuum > Issue Type: Task > Components: Web interface >Reporter: Rahul Thakur > Attachments: CONTINUUM-962.patch, > CONTINUUM-962_new_postsubmit_form.jpg, > CONTINUUM-962_new_unsubmitted_form.jpg, > CONTINUUM-962_original_postsubmit_form.jpg, > CONTINUUM-962_original_unsubmitted_form.jpg > > -- 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-962) Clean up CSS styles for validation/error messages
[ http://jira.codehaus.org/browse/CONTINUUM-962?page=all ] Rahul Thakur updated CONTINUUM-962: --- Attachment: CONTINUUM-962_new_postsubmit_form.jpg Updated: Create Admin Users form with validation/error messages > Clean up CSS styles for validation/error messages > - > > Key: CONTINUUM-962 > URL: http://jira.codehaus.org/browse/CONTINUUM-962 > Project: Continuum > Issue Type: Task > Components: Web interface >Reporter: Rahul Thakur > Attachments: CONTINUUM-962.patch, > CONTINUUM-962_new_postsubmit_form.jpg, CONTINUUM-962_new_unsubmitted_form.jpg > > -- 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-962) Clean up CSS styles for validation/error messages
[ http://jira.codehaus.org/browse/CONTINUUM-962?page=all ] Rahul Thakur updated CONTINUUM-962: --- Attachment: CONTINUUM-962_new_unsubmitted_form.jpg Updated: Create Admin user screen > Clean up CSS styles for validation/error messages > - > > Key: CONTINUUM-962 > URL: http://jira.codehaus.org/browse/CONTINUUM-962 > Project: Continuum > Issue Type: Task > Components: Web interface >Reporter: Rahul Thakur > Attachments: CONTINUUM-962.patch, > CONTINUUM-962_new_postsubmit_form.jpg, CONTINUUM-962_new_unsubmitted_form.jpg > > -- 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-962) Clean up CSS styles for validation/error messages
[ http://jira.codehaus.org/browse/CONTINUUM-962?page=all ] Rahul Thakur updated CONTINUUM-962: --- Attachment: CONTINUUM-962.patch Some updates to validation/error messages and visual elements > Clean up CSS styles for validation/error messages > - > > Key: CONTINUUM-962 > URL: http://jira.codehaus.org/browse/CONTINUUM-962 > Project: Continuum > Issue Type: Task > Components: Web interface >Reporter: Rahul Thakur > Attachments: CONTINUUM-962.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-963) Derby Database initialization error on Webapp restarts on Jetty
[ http://jira.codehaus.org/browse/CONTINUUM-963?page=all ] Rahul Thakur updated CONTINUUM-963: --- Attachment: CONTINUUM-963.patch Upgraded Jetty Maven plugin version to 6.0.1 - error observed with version 6.0.0 > Derby Database initialization error on Webapp restarts on Jetty > > > Key: CONTINUUM-963 > URL: http://jira.codehaus.org/browse/CONTINUUM-963 > Project: Continuum > Issue Type: Bug >Reporter: Rahul Thakur > Attachments: CONTINUUM-963.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: (CONTINUUM-963) Derby Database initialization error on Webapp restarts on Jetty
Derby Database initialization error on Webapp restarts on Jetty Key: CONTINUUM-963 URL: http://jira.codehaus.org/browse/CONTINUUM-963 Project: Continuum Issue Type: Bug Reporter: Rahul Thakur -- 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: (CONTINUUM-962) Clean up CSS styles for validation/error messages
Clean up CSS styles for validation/error messages - Key: CONTINUUM-962 URL: http://jira.codehaus.org/browse/CONTINUUM-962 Project: Continuum Issue Type: Task Components: Web interface Reporter: Rahul Thakur -- 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-140) SNAPSHOT plugin versions are not supported for PDE projects. Error in MANIFEST.MF
[ http://jira.codehaus.org/browse/MECLIPSE-140?page=comments#action_77917 ] Damien Lecan commented on MECLIPSE-140: --- You should have handled the case of qualifiers in version such as beta or RC 2.0.0-beta-1-SNAPSHOT must be rename by 2.0.0.beta-1-SNAPSHOT and not by 2.0.0-beta-1.SNAPSHOT I reported this as a new bug : MECLIPSE-176 > SNAPSHOT plugin versions are not supported for PDE projects. Error in > MANIFEST.MF > - > > Key: MECLIPSE-140 > URL: http://jira.codehaus.org/browse/MECLIPSE-140 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: PDE support >Affects Versions: 2.3 >Reporter: David Boden > Assigned To: fabrizio giustina >Priority: Critical > Fix For: 2.3 > > Attachments: maven-eclipse-plugin-447076.patch, patch.txt > > > If the version declared in your pom.xml is 2.0.0-SNAPSHOT then the following > is written to MANIFEST.MF: > Bundle-Version: 2.0.0-SNAPSHOT > Eclipse complains: > assertion failed: The service (3rd) component of plug-in version identifier, > "2.0.0-SNAPSHOT", must be numeric. > Is the resolution to strip the "-SNAPSHOT" string off the end of the version? -- 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-176) Qualifier in version are not renamed correctly in MANIFEST.MF
Qualifier in version are not renamed correctly in MANIFEST.MF - Key: MECLIPSE-176 URL: http://jira.codehaus.org/browse/MECLIPSE-176 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: PDE support Affects Versions: 2.3 Reporter: Damien Lecan Priority: Critical In MANIFEST.MF, qualifiers in version are not renamed correctly 2.0.0-beta-1-SNAPSHOT must be rename by 2.0.0.beta-1-SNAPSHOT and not by 2.0.0-beta-1.SNAPSHOT In OSGi spec R4 §3.2.4, versions can have a qualifier, but separator must be dot '.', not '-' version ::= major( '.' minor ( '.' micro ( '.' qualifier )? )? )? major ::= number minor ::= number micro ::= number qualifier ::= ( alphanum | '_' | '-' )+ For a patch, see maven-eclipse-plugin-447076.patch in MECLIPSE-140 -- 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: (MNGECLIPSE-203) Maven Eclipse Plugin fails to read POM while command line works
Maven Eclipse Plugin fails to read POM while command line works --- Key: MNGECLIPSE-203 URL: http://jira.codehaus.org/browse/MNGECLIPSE-203 Project: Maven 2.x Extension for Eclipse Issue Type: Bug Components: Dependency Resolver Affects Versions: 0.0.10 Reporter: Yuri Schimke I have got this error a couple of times in eclipse, but things are working well in the command line. To fix it I tried deleting and reverting the mentioned POM files, but in the end restarting eclipse was the only thing to fix it. Severity and DescriptionPathResourceLocation Creation Time Id Unable to get dependency information: Unable to read the metadata file for artifact 'XXX:etl:jar': Cannot find parent: XXX:XXX-MODULES for project: XXX:XXXServer:pom:1.2.1-SNAPSHOT XXX:etl:jar:1.2.1-SNAPSHOT from the specified remote repositories: Maven Snapshots (http://snapshots.maven.codehaus.org/), central (http://ibiblio.org/maven2), internal-snapshot (XXX), internal-3rdparty (XXX), internal-released (XXX), mergere (http://repo.mergere.com/maven2) Path to dependency: 1) XXX:data_server:jar:1.2.1-SNAPSHOT XXX Data Server pom.xml line 1 1161087949549 186247 -- 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-175) Error message "Unable to index ...pom. Cannot delete workspace\.metadata\.plugins\org.maven.ide.eclipse\index\local\_gf.cfs"
Error message "Unable to index ...pom. Cannot delete workspace\.metadata\.plugins\org.maven.ide.eclipse\index\local\_gf.cfs" Key: MECLIPSE-175 URL: http://jira.codehaus.org/browse/MECLIPSE-175 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.3 Reporter: Aaron Digulla I saw this during a build. The cause seems to be that the file doesn't exist in the first place. Should be trivial to fix. -- 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-174) Plugin doesn't cache "source not available" status
Plugin doesn't cache "source not available" status -- Key: MECLIPSE-174 URL: http://jira.codehaus.org/browse/MECLIPSE-174 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.3 Reporter: Aaron Digulla Priority: Minor When the m2 plugin reads the POM files and "Download sources" is set in the Eclipse preferences, it tries to download the source every time. Instead, it should cache the "source not available" status somewhere (just like Maven itself does) and not print thousands of error messages (Unable to download the artifact from any repository). This also delays the build considerably (opening network connections) and real errors are drowned. -- 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
