You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Simon Massey (JIRA)" <ji...@codehaus.org> on 2011/04/03 21:43:22 UTC

[jira] Created: (MRELEASE-671) release tag for maven-release-2.1 does not have src to match released jar

release tag for maven-release-2.1 does not have src to match released jar
-------------------------------------------------------------------------

                 Key: MRELEASE-671
                 URL: http://jira.codehaus.org/browse/MRELEASE-671
             Project: Maven 2.x Release Plugin
          Issue Type: Improvement
    Affects Versions: 2.1
         Environment: any
            Reporter: Simon Massey


If you checkout the maven-release-2.1 code as per anon access svn url on the project page here:

http://maven.apache.org/plugins/maven-release-plugin/source-repository.html

Then the code does not compile as it is missing source. If you take a look at this folder:  

http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1/maven-release-manager/src/main/java/org/apache/maven/shared/release/config/

it does not contain ReleaseDescriptor.java yet that class is included in the maven-release-manager-2.1-sources.jar and maven-release-manager-2.1.jar on central and is required to compile the projects as checked out from that url. 


-- 
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: (MRELEASE-671) release tag for maven-release-2.1 does not have src to match released jar

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MRELEASE-671.
---------------------------------

    Resolution: Not A Bug
      Assignee: Brett Porter

that source file is generated at build time. I presume by "doesn't compile", you mean that you opened it in an IDE that doesn't recognise the Maven project, so the generate sources phase has not been executed?

> release tag for maven-release-2.1 does not have src to match released jar
> -------------------------------------------------------------------------
>
>                 Key: MRELEASE-671
>                 URL: http://jira.codehaus.org/browse/MRELEASE-671
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.1
>         Environment: any
>            Reporter: Simon Massey
>            Assignee: Brett Porter
>
> If you checkout the maven-release-2.1 code as per anon access svn url on the project page here:
> http://maven.apache.org/plugins/maven-release-plugin/source-repository.html
> Then the code does not compile as it is missing source. If you take a look at this folder:  
> http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1/maven-release-manager/src/main/java/org/apache/maven/shared/release/config/
> it does not contain ReleaseDescriptor.java yet that class is included in the maven-release-manager-2.1-sources.jar and maven-release-manager-2.1.jar on central and is required to compile the projects as checked out from that url. 

-- 
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