headers
Karl Heinz Marbaise (JIRA | 1 May 2012 13:34

[jira] (MJDIFF-12) jdiff fails during creation of report - Cannot find doclet class jdiff.JDiff

Karl Heinz Marbaise created MJDIFF-12:
-----------------------------------------

             Summary: jdiff fails during creation of report - Cannot find doclet class jdiff.JDiff
                 Key: MJDIFF-12
                 URL: https://jira.codehaus.org/browse/MJDIFF-12
             Project: Maven 2.x JDiff Plugin
          Issue Type: Bug
    Affects Versions: 1.0-beta-2
         Environment: Maven 3.0.4:
kama <at> office:~/ws-git/sapm$ mvn --version
Apache Maven 3.0.4 (r1209000; 2011-12-01 09:49:38+0100)
Maven home: /home/kama/tools/maven
Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-41-generic", arch: "i386", family: "unix"

Maven 3.0.3:
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: /home/kama/tools/maven
Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-41-generic", arch: "i386", family: "unix"

Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_26
Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
Default locale: en_US, platform encoding: UTF-8
(Continue reading)

Permalink | Reply | 6 comments |
headers
Karl Heinz Marbaise | 1 May 2012 13:34
Picon
Picon

Re: [VOTE] [CANCELED] Release JDiff-maven-plugin version 1.0-beta-1

Hi Robert,

> Can you both create a jira-issue for it?
Done MJDIFF-12..

Kind regards
Karl Heinz Marbaise
--

-- 
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 Würselen                           http://www.soebes.de

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 0 comments |
headers
Niklas Gustavsson (JIRA | 1 May 2012 19:32

[jira] (MCLIRR-47) Support "bundle" packaging

Niklas Gustavsson created MCLIRR-47:
---------------------------------------

             Summary: Support "bundle" packaging
                 Key: MCLIRR-47
                 URL: https://jira.codehaus.org/browse/MCLIRR-47
             Project: Maven 2.x Clirr Plugin
          Issue Type: Improvement
    Affects Versions: 2.4
            Reporter: Niklas Gustavsson

Similar to MCLIRR-39, the clirr plugin does not support the packaging type "bundle", which are also
ordinary JARs. Could that packaging type be added to the list of types to check as in MCLIRR-39?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 0 comments |
headers
Mark Koch (JIRA | 1 May 2012 21:25

[jira] (MRPM-112) Build should fail if keyName or keyPassphrase configuration elements specify invalid values

Mark Koch created MRPM-112:
------------------------------

             Summary: Build should fail if keyName or keyPassphrase configuration elements specify invalid values
                 Key: MRPM-112
                 URL: https://jira.codehaus.org/browse/MRPM-112
             Project: Mojo RPM Plugin
          Issue Type: Bug
          Components: rpm
    Affects Versions: 2.1-alpha-1
         Environment: Centos 6.2
            Reporter: Mark Koch
         Attachments: RPMSigner.patch

When configuring the plugin for RPM signing, if an invalid keyName or keyPassphrase is specified, the
signing of the rpm is skipped.  In these cases the build produces an artifact that does not meet the
specifications provided in the pom ( it's not signed ).  This should result in the failure of the build.  

<pre>
[INFO] spawn rpm --define _gpg_name Non-Existent-Keyname --addsign rpm-signing-test-1.0.0-SNAPSHOT20120501162200.noarch.rpm
[INFO] Enter pass phrase: 
[INFO] gpg: skipped "Non-Existent-Keyname": No secret key
[INFO] gpg: signing failed: No secret key
[INFO] Pass phrase check failed
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
</pre>

--
(Continue reading)

Permalink | Reply | 3 comments |
headers
Mark Koch (JIRA | 1 May 2012 21:29

[jira] (MRPM-112) Build should fail if keyName or keyPassphrase configuration elements specify invalid values


     [
https://jira.codehaus.org/browse/MRPM-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Koch updated MRPM-112:
---------------------------

    Attachment: pom.xml

Simple test POM.  mvn package on this pom should result in an unsuccessful build.

> Build should fail if keyName or keyPassphrase configuration elements specify invalid values
> -------------------------------------------------------------------------------------------
>
>                 Key: MRPM-112
>                 URL: https://jira.codehaus.org/browse/MRPM-112
>             Project: Mojo RPM Plugin
>          Issue Type: Bug
>          Components: rpm
>    Affects Versions: 2.1-alpha-1
>         Environment: Centos 6.2
>            Reporter: Mark Koch
>         Attachments: pom.xml, RPMSigner.patch
>
>
> When configuring the plugin for RPM signing, if an invalid keyName or keyPassphrase is specified, the
signing of the rpm is skipped.  In these cases the build produces an artifact that does not meet the
specifications provided in the pom ( it's not signed ).  This should result in the failure of the build.  
> <pre>
> [INFO] spawn rpm --define _gpg_name Non-Existent-Keyname --addsign rpm-signing-test-1.0.0-SNAPSHOT20120501162200.noarch.rpm
(Continue reading)

Permalink | Reply | 0 comments |
headers
Olivier Lamy (JIRA | 1 May 2012 22:21

[jira] (MBUILDNUM-92) Git buildId fails when Maven is invoked from another process (e.g NetBeans or packaging scripts)


     [
https://jira.codehaus.org/browse/MBUILDNUM-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed MBUILDNUM-92.
---------------------------------

    Resolution: Fixed
      Assignee: Olivier Lamy

> Git buildId fails when Maven is invoked from another process (e.g NetBeans or packaging scripts)
> ------------------------------------------------------------------------------------------------
>
>                 Key: MBUILDNUM-92
>                 URL: https://jira.codehaus.org/browse/MBUILDNUM-92
>             Project: Mojo Build Number Maven Plugin
>          Issue Type: Bug
>    Affects Versions: buildnumber-maven-plugin-1.0
>         Environment: RHEL 5.5, OSX 10.6.8
>            Reporter: Jakub Skoczen
>            Assignee: Olivier Lamy
>             Fix For: 1.1
>
>         Attachments: trace.txt
>
>
> Git is present on the path and standard 'mvn buildnumber:create" works, but invoking the goal from within
IDE/Makefile/RPM scripts fails with: 
> [DEBUG] Configuring mojo 'org.codehaus.mojo:buildnumber-maven-plugin:1.0:create' -->
> [DEBUG]   (s) buildNumberPropertiesFileLocation = /home/jakub/rpmbuild/BUILD/masterkey-torus2-2.9/buildNumber.properties
(Continue reading)

Permalink | Reply | 0 comments |
headers
Javier Murciego (JIRA | 1 May 2012 22:32

[jira] (MWAS-19) Create a complete set of integration-tests


     [
https://jira.codehaus.org/browse/MWAS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Javier Murciego closed MWAS-19.
-------------------------------

    Resolution: Fixed

I created a set of test for most of the goals. All posible combinations was6, was61 or  was70, Oracle/Sun JDK
or IBM JDK and Maven 2 or Maven 3 are tested in Linux and Windows through profiles and scripts.

> Create a complete set of integration-tests
> ------------------------------------------
>
>                 Key: MWAS-19
>                 URL: https://jira.codehaus.org/browse/MWAS-19
>             Project: Maven 2.x WebSphere 6 Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.0
>         Environment: N/A
>            Reporter: David J. M. Karlsen
>            Assignee: Javier Murciego
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Although I use the plugin frequently in a lot of projects integration tests should be added for all of the goals.
> Preferably activated by a profile by an existing path to a WAS installation and/or a variable.
> Either use the shitty-plugin or the invoker-plugin - whatever suits our need best.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Olivier Lamy | 1 May 2012 23:08
Picon
Favicon
Gravatar

[VOTE] Release Maven Buildnumber plugin version 1.1

Hi,

I'd like to release version Maven Buildnumber plugin version 1.1

We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12124&version=17319

Staging Repositories:
General:  https://nexus.codehaus.org/content/groups/staging/
Exclusive: https://nexus.codehaus.org/content/repositories/orgcodehausmojo-067/

(Staging) Site:
http://mojo.codehaus.org/buildnumber-maven-plugin/

 [ ] +1
 [ ] +0
 [ ] -1

The vote is open for 72 hours and will succeed by lazy consensus.

Here my +1

Thanks
--

-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

---------------------------------------------------------------------
To unsubscribe from this list, please visit:
(Continue reading)

Permalink | Reply | 1 comment |
headers
zhouxingxing (JIRA | 2 May 2012 02:51

[jira] (MCOBERTURA-161) cobertura report appear a lot of error : JavaNCSS got an error while parsing the java file


    [
https://jira.codehaus.org/browse/MCOBERTURA-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297651#comment-297651
] 

zhouxingxing commented on MCOBERTURA-161:
-----------------------------------------

if(strRet.equals("01"))         
return SUCCESS;     
else{         
if(strRet.equals("02"))             
this.strError = "&#24050;&#34987;&#28608;&#27963;";         
if(strRet.equals("03"))            
 this.strError = "&#26410;&#34987;&#28608;&#27963;";         
if(strRet.equals("04"))             
this.strError = "&#27809;&#26377;&#36825;&#20010;&#29992;&#25143;";         
return ERROR;     
Appear afore-mentioned reason is the program has a lot of Chinese message (utf-8) code (such as the above
code), cobertura instrument compiled not pass, online information in ()The bat files
(cobertura-instrument.bat) add "-Dfile.encoding=utf-8" encoding or Java environment variable add
"-Dfile.encoding=utf-8" encoding can be solved, but I'm in ant build.xml,I add a lot of encoding =
"utf-8" didn't solve. Please you advice!&#12290;

                
> cobertura report  appear a lot of  error : JavaNCSS got an error while parsing the java file 
> ---------------------------------------------------------------------------------------------
>
>                 Key: MCOBERTURA-161
>                 URL: https://jira.codehaus.org/browse/MCOBERTURA-161
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mikhail Mazursky (JIRA | 2 May 2012 08:01

[jira] (MCASSANDRA-18) Support Cassandra 1.1

Mikhail Mazursky created MCASSANDRA-18:
------------------------------------------

             Summary: Support Cassandra 1.1
                 Key: MCASSANDRA-18
                 URL: https://jira.codehaus.org/browse/MCASSANDRA-18
             Project: Mojo's Cassandra Maven Plugin
          Issue Type: New Feature
    Affects Versions: 1.0.0-1
            Reporter: Mikhail Mazursky
            Assignee: Stephen Connolly

Release a new version of plugin that spawns Cassandra 1.1 instance(s).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 1 comment |

Gmane