Re: [jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
On Thu, Oct 8, 2009 at 10:22 AM, Kathey Marsden wrote: > Ian McCall (JIRA) wrote: >> >> Just built a project using 10.5.3.0_1 - all working fine here. >> > > Hooray! Thanks everyone for their hard work and perseverance on this. It > makes me almost thankful 10.5.2 got pulled so I didn't have to try to do it. > Many, many thanks from me too. Myrna
Re: [jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
Ian McCall (JIRA) wrote: Just built a project using 10.5.3.0_1 - all working fine here. Hooray! Thanks everyone for their hard work and perseverance on this. It makes me almost thankful 10.5.2 got pulled so I didn't have to try to do it.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763477#action_12763477 ] Ian McCall commented on DERBY-4267: --- Just built a project using 10.5.3.0_1 - all working fine here. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > derby-4267-2c-using_ant_task.diff, maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763459#action_12763459 ] Kristian Waagan commented on DERBY-4267: I was able to pull down some of the Derby 10.5.3.0_1 artifacts and use them in a trivial test project, so they seem to be live. Let's wait and see what our users have to report :) I won't be surprised if we have to improve the POMs later, but let us deal with issues as they are reported. Hopefully people will choose the 10.5.3.0_1 version over 10.5.3.0, since the latter artifacts are invalid. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > derby-4267-2c-using_ant_task.diff, maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763247#action_12763247 ] Knut Anders Hatlen commented on DERBY-4267: --- As to the signatures that change, they contain a timestamp, which can be seen when you verify them: $ gpg --verify db-derby-10.5.3.0-lib.tar.gz.asc gpg: Signature made Mon Aug 10 22:21:25 2009 CEST using DSA key ID 98E21827 gpg: Good signature from "Rick Hillegas " > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > derby-4267-2c-using_ant_task.diff, maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763128#action_12763128 ] Kristian Waagan commented on DERBY-4267: Hi RIck, I checked the files at the ibiblio rsync area, and it looks good. You may want to give the group write access, but since this is a "write-once media" (with respect to the artifacts being distributed/rsync'ed) it's not a big deal. The files haven't been distributed to the central repos yet, but I'll give it another try tomorrow. Thanks, > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > derby-4267-2c-using_ant_task.diff, maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763104#action_12763104 ] Rick Hillegas commented on DERBY-4267: -- The 2c patch looks good to me. I have re-generated the 10.5.3.0_1 distribution. This new version has checksums for the pom in derby-project. I compared the new rev to the previous rev, and the differences were what I expected except for this: the gpg signatures (the .asc) files changed. I have confirmed that if I use gpg to generate two signatures on the same file, then the signatures are different. I did not know that the signature computation was time-sensitive. I have verified the signatures so I'm prepared to believe that what I am seeing is expected. I have deployed the new 10.5.3.0_1 distribution to the ibiblio rsync area. It should be picked up and copied to the Maven 2 repository. Hopefully, this distribution will be useful to Maven users and will not raise any warnings. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > derby-4267-2c-using_ant_task.diff, maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763012#action_12763012 ] Kristian Waagan commented on DERBY-4267: Hi Rick, I have no strong opinions on the issue. I'm fine with the path of least resistance: keeping the tag unchanged. Regarding your item (2), I'm not sure what the scm-tag offers with respect to specifying a revision. That's another data point suggesting we keep things as they are and get the new artifacts published sooner than later. You may have done this already, but if you use the newest patch, it would be good if you could keep the previous artifacts tested by Tony Jewell (see comment somewhere above) and compare the next rev with those. I think you should observe the following differences: - the derby.version property has been deleted from the top-level POM. - the workaround for the install plugin bug has been added in the top-level POM - all checksums of the signature files (*.asc) are gone - derby-project-VERSION.pom should have checksums (sha1 and md5) Good luck! I think we're getting close to the finishing line now :) > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > derby-4267-2c-using_ant_task.diff, maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763002#action_12763002 ] Kristian Waagan commented on DERBY-4267: Hello Benson, This is a known issue, and we're in the process of deploying a new set of Derby 10.5.3.0 artifacts. The latest test artifacts we are testing are at http://people.apache.org/~rhillegas/repository/org/apache/derby/ , but I think they will be regenerated once more due to some missing checksums (caused by a bug in maven-install-plugin). As far as I have understood, the next deployed artifacts will have version 10.5.3.0_1, because it is not possible (either technically or by policy, I don't know) to refresh an already deployed set of artifacts. I'm not the one deploying the artifacts, but I'm under the impression it is being worked on actively. We've had several other users reporting the error already, so we're aware it is causing people trouble. Regards, > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > derby-4267-2c-using_ant_task.diff, maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[
https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762681#action_12762681
]
Benson Margulies commented on DERBY-4267:
-
There are broken artifacts at central. They have variable references in places
where they are not supposed to be.
Downloading:
http://repo1.maven.org/maven2/org/apache/derby/derby-project/${derby.version}/derby-project-${derby.version}.pom
[INFO] Unable to find resource
'org.apache.derby:derby-project:pom:${derby.version}' in repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
> Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
> --
>
> Key: DERBY-4267
> URL: https://issues.apache.org/jira/browse/DERBY-4267
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Affects Versions: 10.5.1.1, 10.6.0.0
>Reporter: H.-Dirk Schmitt
> Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat,
> derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat,
> derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat,
> derby-4267-2c-using_ant_task.diff, maven2.zip
>
>
> Only 10.4.2.0 and older are available in the maven 2 repositories.
> May you please also provide the new version.
> Please see also https://issues.apache.org/jira/browse/DERBY-4220
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762665#action_12762665 ] Rick Hillegas commented on DERBY-4267: -- Hi Kristian, I can see that this could be a religious discussion. From your description of how this element is used, the following answers make sense to me: 1) could be a pointer to the head of the development codeline. That is what the element describes now. 2) could point at the svn tag for the release, the exact source code used to build the artifacts. Pointing at the head of the release branch falls somewhere between (1) and (2) and seems to me to be harder to motivate than the options above. In any event, I'm fine with your current solution, (1). And I know nothing. So take my advice at your peril! > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > derby-4267-2c-using_ant_task.diff, maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762629#action_12762629 ] Kristian Waagan commented on DERBY-4267: Hi Rick, Your last reply confuses me slightly. The derby.version element has to go away, because it doesn't work as intended. I don't think we should hold our breath for a solution to the problem either. The person generating the artifacts will have to insert the correct Derby version number in each and every POM. This can be done easier by using for instance Perl or sed. I'll rephrase my question. When we deploy artifacts for the next 10.4 update release, should the scm tag point to the 10.4 branch? When we deploy artifacts for the next 10.5 update release, should the scm tag point to the 10.5 branch? Since we currently doesn't deploy artifacts for trunk (which would have had to be snapshots I suppose?), the scm tag of our official Maven artifacts will never point to trunk. For an example on how the scm tag can be used, let's take NetBeans and a project where you have specified the Derby Maven artifacts as dependencies. In that case, you can choose to check out or browse the source code of Derby by right clicking the icon representing the Maven artifact. Do we want to point our users to the trunk (Derby development version), or to the branch of the official Derby version being used? In any case, this is a rather minor matter :) > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > derby-4267-2c-using_ant_task.diff, maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762620#action_12762620 ] Rick Hillegas commented on DERBY-4267: -- Thanks for the quick response, Kristian. I will test-drive the 2c patch today. >One issue remains (I brought it up before): >Do we want to point to the 10.5 branch, or to trunk in the source code >repository property for 10.5? >Currently it points at trunk, but that can easily be changed in the top level >POM (see the scm tag). This is just my $.02 since I don't know anything about how this pom is used. I think that what you have right now is at least internally consistent. The source code url agrees with the element lower down, whose contents are "trunk-alpha". If you change one, then I think that you should change the other. Most of the information in this pom is project-wide. That is, it's true regardless of the version of Derby you're seeking. For that reason too I think that the and elements look good. Thanks. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > derby-4267-2c-using_ant_task.diff, maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762616#action_12762616 ] Kristian Waagan commented on DERBY-4267: Note that the new version of the install plugin doesn't generate checksums for the signature files. That is, the following files are no longer generated: pomfile.asc.md5 pomfile.asc.sha1 jarfile.asc.md5 jarfile.asc.sha1 >From an earlier discussion on this issue we saw projects both with and without >these files. Maybe the differences were caused by the various projects using >different versions of the install plugin? > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > derby-4267-2c-using_ant_task.diff, maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762299#action_12762299 ] Rick Hillegas commented on DERBY-4267: -- Thanks for test-driving the 10.5.3.0_1 distribution, Tony. I can see that there is no checksum for the pom in the derby-project/10.5.3.0_1 directory. Hi Kristian, All of the artifact directories which I have inspected (except for derby-project/10.5.3.0_1) have the following files associated with the pom: pomfile pomfile.asc pomfile.asc.md5 pomfile.asc.sha1 pomfile.md5 pomfile.sha1 The derby-project/10.5.3.0_1 has these files: pomfile pomfile.asc pomfile.asc.md5 pomfile.asc.sha1 As you can see, derby-project/10.5.3.0 is missing these files: pomfile.md5 pomfile.sha1 Do you have any theories about why the checksums weren't generated for these files? Thanks, -Rick > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762247#action_12762247 ] Tony Jewell commented on DERBY-4267: Rick, Thanks for doing that - I have finally gotten round to testing with your patched distro (10.5.3.0_1). Maven downloaded correctly from the artifacts in your repo and I have run my unit tests to completion with no problems. Only issue I got was on a checksum: Downloading: http://people.apache.org/~rhillegas/repository/org/apache/derby/derby-project/10.5.3.0_1/derby-project-10.5.3.0_1.pom 6K downloaded (derby-project-10.5.3.0_1.pom) [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for org/apache/derby/derby-project/10.5.3.0_1/derby-project-10.5.3.0_1.pom - IGNORING Am lookng fwd to your getting this into the offiicial repo as it means we can start to use the FETCH/OFFSET clauses on queries introduced in 10.5 Thx, Tony Jewell > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760979#action_12760979 ] Rick Hillegas commented on DERBY-4267: -- I have created a new Maven distribution called 10.5.3.0_1 and staged it at http://people.apache.org/~rhillegas/repository/org/apache/derby/ This distribution contains the Derby 10.5.3.0 jars plus better poms. Please test-drive this distribution. If users think that it's a good Maven packaging of Derby artifacts, then I can copy it to the ibiblio directory tree so that it will be sync'd to the Maven 2 repository. For an explanation of why I generated a new Maven version id, please see the commentary on derby-4390. Thanks, -Rick > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760969#action_12760969 ] m commented on DERBY-4267: -- Any updates on this? I am blocked from upgrading to 10.5.x. If it is further delayed it may no longer be an option since it will be too close to our release freeze date. Thanks. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758883#action_12758883 ] Tony Jewell commented on DERBY-4267: Likewise, thanks for your work on this - it is very much appreciated! I will be trying your fix ASAP. And - my very best wishes for a speedy recovery, Kristian. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758419#action_12758419 ] Ian McCall commented on DERBY-4267: --- Thanks for that - will try the new artefact tomorrow and report back. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[
https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758411#action_12758411
]
Rick Hillegas commented on DERBY-4267:
--
I have hand-replaced the ${derby.version} variables with the literal "10.5.3.0"
and regenerated the signed artifacts. I tar'd them up and copied them to
people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository.
Hopefully, they will be rsync'd to the maven2 repository and be usable.
I tried a couple more experiments in using maven to deploy the artifacts but I
could not get either scp or scpexe to work. For the record, I can ssh and sftp
to people.apache.org without giving my password because I have setup a public
key for my machine on people.apache.org.
When the top level pom (maven2/pom.xml) gives the deployment url as
scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
deployment fails with this message:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error deploying artifact: Authentication failed: Cannot connect. Reason:
Algorithm negotiation fail
When I change scp to scpexe so that the deployment url is
scpexe://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository
deployment fails with this message:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error deploying artifact: Error executing command for transfer
Exit code 255 - Permission denied (publickey,keyboard-interactive).
In case it matters, I am running on a Macbook Pro laptop running Mac OS X
version 10.5.7.
> Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
> --
>
> Key: DERBY-4267
> URL: https://issues.apache.org/jira/browse/DERBY-4267
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Affects Versions: 10.5.1.1, 10.6.0.0
>Reporter: H.-Dirk Schmitt
> Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat,
> derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat,
> derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat,
> maven2.zip
>
>
> Only 10.4.2.0 and older are available in the maven 2 repositories.
> May you please also provide the new version.
> Please see also https://issues.apache.org/jira/browse/DERBY-4220
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[
https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757399#action_12757399
]
Kristian Waagan commented on DERBY-4267:
Hi m,
The placeholder will only exist in Derby's source code repository.
When a release is cut, it will be replaced by a specific Derby version number -
for instance 10.5.3.0.
The only purpose of the placeholder is to make it easier for the person
generating the Maven artifacts to do a search and replace to insert the correct
version number.
There are quite a few POMs, and doing it manually is a bit tedious.
The process above is generally what I would have expected the Maven install
plugin to do, using the ${derby.version} variable.
Instead of a placeholder, maybe we could just the current version number, but
it may incur a little extra work as we generate release candidates (that we
don't actually release).
Thanks for the feedback,
> Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
> --
>
> Key: DERBY-4267
> URL: https://issues.apache.org/jira/browse/DERBY-4267
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Affects Versions: 10.5.1.1, 10.6.0.0
>Reporter: H.-Dirk Schmitt
> Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat,
> derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat,
> derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat,
> maven2.zip
>
>
> Only 10.4.2.0 and older are available in the maven 2 repositories.
> May you please also provide the new version.
> Please see also https://issues.apache.org/jira/browse/DERBY-4220
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757283#action_12757283 ] m commented on DERBY-4267: -- Hi Kristian, I hope you a speedy recovery. I don't understand your suggestion for a placeholder for the version. Maven will require a specific version number in the version tag. The poms will need to be redeployed with the specific version number for maven to sucessfully process the poms. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757075#action_12757075 ] Kristian Waagan commented on DERBY-4267: Hi all, I'm still on sick leave, and is restricted to typing with one arm only, but I thought I should share a few of my thoughts on this issue. After searching the Maven forums, it appears I have led us into one of Maven's quagmires. What I instinctively tried to do (I haven't used Maven before), isn't yet supported and it seems fixing it isn't straight forward. The limitation/problem has been known for quite some time. Due to a reboot I managed to loose my references to the relevant JIRAs, but I can dig them up again later. I suggest we take action to fix the problem our users are experiencing by inserting the version in the POM "manually". Since there are quite a few POMs to edit, maybe inserting a placeholder would be good? Then people can use whichever tool they're familiar with on their platform to replace the placeholder with an actual version (on *nix this could be perl or sed). Note that the already deployed POMs shouldn't be edited, because that would mess up the checksums. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756710#action_12756710 ] Ian McCall commented on DERBY-4267: --- Thanks for the update, and please pass on the very best to Kristian. Ian > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756660#action_12756660 ] Rick Hillegas commented on DERBY-4267: -- Hi Tony and Ian, We are experiencing technical difficulties. Kristian, who prepared the patch, had a serious accident and is out of the office for a while. In the meantime, my machine is up on the blocks and won't be repaired for a couple more days. I'll take a look at hand-repairing the poms when my machine comes back. -Rick > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756422#action_12756422 ] Ian McCall commented on DERBY-4267: --- Another voice in favour of a resolution to this one please - similar reasons to the previous comment, there's 10.5.x functionality we're looking for but we can't get access to it via our standard build process. Thanks in advance for the help. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756099#action_12756099 ] Tony Jewell commented on DERBY-4267: This is holding up our development as we we require the Fetch and Offset query clauses introduced in 10.5. We are currently stalled on maven build and deploy as the 10.5.3.0 pom has this issue. If you could deploy a temporary fix (by putting in the versions) it would allow us to move forward. Thanks! > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754114#action_12754114 ] Rick Hillegas commented on DERBY-4267: -- The following conversation happened on irc after I hand-deployed the artifacts: hi where's the largest derby chan? I think I've seen a larger one once there's an error in the lastest pom * ahfeel ([email protected]) has left #derby [ERROR] FATAL ERROR [INFO] Invalid uri 'http://repo1.maven.org/maven2/org/apache/derby/derby-project/${derby.version}/derby-project-${derby.version}.pom': escaped absolute path not valid http://repo1.maven.org/maven2/org/apache/derby/derby/10.5.3.0/derby-10.5.3.0.pom contains ${derby.version} it would be cool if anyone could fix this oxi: You may want to add that comment here: https://issues.apache.org/jira/browse/DERBY-4267 kahatlen: thanks is there a maven repository with a fixed pom? oxi: I don't think so. from the latest comment on the jira issue, it seems like there were problems getting 10.5.3.0 deployed. I haven't followed the discussion closely, but I think someone is getting really close to making it work now :) kahatlen: I see. I have looked inside the poms and they all have this error. That is, instances of derby.version were not replaced with 10.5.3.0. It seems that if you set derby.version on the java command line when you run mvn, the version is picked up when the file names of the artifacts are created but the version number is not substituted into the contents of the poms. I don't think that I should fix these poms by hand. I think we should improve the patch to handle this and then redeploy. I don't know if there is any harm in leaving the broken poms in the repository until we can post fixed poms. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753778#action_12753778 ] Rick Hillegas commented on DERBY-4267: -- I tried using the patch to deploy to the maven2 repository, but was stymied by authentication problems. I issued the following command: mvn "-Dgpg.passphrase=$PASSPHRASE" -Dderby.version=10.5.3.0 -Dmy_login=rhillegas -Dmy_password=$APACHE_PASSWORD clean deploy I also tried leaving off the login and password properties and, instead, hardwiring them into settings.xml. In both cases, deployment failed with the following exception: [INFO] Error deploying artifact: Authentication failed: Cannot connect. Reason: Algorithm negotiation fail Based on my bad experience with deployment under maven1, I abandoned this approach. Instead, I tar'd up the artifacts, copied the tarball to people.apache.org and untar'd the contents under /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache I changed the group ownership of the artifacts to apcvs and gave the group write access to the top level directory. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753723#action_12753723 ] Rick Hillegas commented on DERBY-4267: -- Scotch that last comment. I was poking around in the old maven directory, not in the new maven2 directory. In the maven2 directory, the patch uses the m2 repository in pom.xml. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753702#action_12753702 ] Rick Hillegas commented on DERBY-4267: -- Thanks, Kristian. The FAQ you pointed me at suggests that we should deploy to /www/people.apache.org/repo/m2-ibiblio-rsync-repository/ rather than /www/people.apache.org/repo/m1-ibiblio-rsync-repository/ The patch looks like it is going to deploy to the second location--at least that's the setting of maven.repo.apache.directory in maven/project.properties. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749427#action_12749427 ] Kristian Waagan commented on DERBY-4267: Rick, does this help? http://apache.org/dev/repository-faq.html > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748448#action_12748448 ] Rick Hillegas commented on DERBY-4267: -- A little more information. I see that the repo1.maven.org repository has directories for the following projects, which are not present in the proposed repository: apache derby felix jdo openejb rat shindig wink xmlrpc Maybe someone pushes artifacts from people.apache.org to repo1.maven.org and the extra projects have some other backdoor arrangement with the maven repository. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748438#action_12748438 ] Rick Hillegas commented on DERBY-4267: -- Thanks for that explanation, Kristian. I think the checksummed signatures are goofy but harmless. I agree that we can leave this alone since other projects tolerate the goofiness too. By the way, I noticed that all of the projects you cited, except for shindig, have artifacts at the deployment location you're proposing: people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository'. I don't understand the relationship between that deployment location and the repositories you just cited, which are all on repo1.maven.org, not people.apache.org. For the record, my apache credentials work on people.apache.org but not on repo1.maven.org. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748307#action_12748307 ] Kristian Waagan commented on DERBY-4267: Hi Rick, I don't think you are doing anything wrong. I can't see ane "*.asc.asc" files in your list. Here's what I think is happening: 1) You generate the "real artifacts", typically a jar file and a POM. 2) These are then signed, resulting in two more files (*.asc) You now have four files. 3) In the install/deployment step, you are checksumming all the artifacts you have. The jar, the jar signature, the POM, and the POM signature. All in all, with two "real artifacts", you end up with twelve files as you described. This because there are two checksums for each artifact (md5 and sha1). Checking the following random projects that sign their artifacts, this seems to be the way it is done: - http://repo1.maven.org/maven2/org/apache/maven/maven-ant-tasks/2.0.6/ - http://repo1.maven.org/maven2/org/apache/httpcomponents/httpclient/4.0/ - http://repo1.maven.org/maven2/org/apache/shindig/shindig-common/1.0-incubating/ - http://repo1.maven.org/maven2/org/apache/tomcat/jasper/6.0.20/ However, these projects don't (no checksumming of the signatures): - http://repo1.maven.org/maven2/org/apache/hadoop/avro/1.0.0/ - http://repo1.maven.org/maven2/org/apache/lucene/lucene-core/2.4.1/ Personally I would prefer to keep the scripts simple instead of writing more code/XML to delete some of the checksum files. Or is there a way to specify files to exclude? > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748096#action_12748096 ] Rick Hillegas commented on DERBY-4267: -- Thanks again for the 2b patch, Kristian. By liberally using -D arguments, I was able to test-drive the clean and install targets without having to edit the scripts themselves. This is what I did: mvn "-Dgpg.passphrase=$PASSPHRASE" -Dderby.version=$RELEASE clean install That filled a local directory tree with artifacts, signatures, and checksums. I verified one of the signatures. However, I am seeing the checksummed signature problem to which the README alluded. For instance, the directory ".m2/repository/org/apache/derby/derby/10.5.3.0" contains the following files: derby-10.5.3.0.jar derby-10.5.3.0.jar.asc derby-10.5.3.0.jar.asc.md5 derby-10.5.3.0.jar.asc.sha1 derby-10.5.3.0.jar.md5 derby-10.5.3.0.jar.sha1 derby-10.5.3.0.pom derby-10.5.3.0.pom.asc derby-10.5.3.0.pom.asc.md5 derby-10.5.3.0.pom.asc.sha1 derby-10.5.3.0.pom.md5 derby-10.5.3.0.pom.sha1 I expected to see only derby-10.5.3.0.jar derby-10.5.3.0.jar.asc derby-10.5.3.0.jar.md5 derby-10.5.3.0.jar.sha1 derby-10.5.3.0.pom derby-10.5.3.0.pom.asc derby-10.5.3.0.pom.md5 derby-10.5.3.0.pom.sha1 Any idea what I'm doing wrong? Thanks, -Rick > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747988#action_12747988 ] Rick Hillegas commented on DERBY-4267: -- Thanks, Kristian. I will test-drive the 2b patch. In the meantime, I have asked the pmc for advice about where to deploy the artifacts. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > derby-4267-2b-using_ant_task.diff, derby-4267-2b-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747804#action_12747804 ] Julien HENRY commented on DERBY-4267: - 1) To sign the artifacts you can use the GPG plugin. http://maven.apache.org/plugins/maven-gpg-plugin/usage.html I think this is what is used for all Maven plugins themself. http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?view=co 2) To have your Maven artifacts ultimately on central there are several possibilities. Either host yourself a server where you can put your files. Maven is able to deploy using ssh, ftp, webdav, ... For example for JWebUnit project we are deploying next to Sourceforge site files via ssh (http://jwebunit.sourceforge.net/m2-repo/). Then you can ask Maven team to replicate your repo on the central. The other option is to ask for a repo on Nexus OpenSource (http://nexus.sonatype.org/oss-repository-hosting.html) > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747626#action_12747626 ] Rick Hillegas commented on DERBY-4267: -- This is the structure of the artifact tree (without signatures and checksums). Looks good to me, but what do I know? ./derby ./derby/10.5.3.0 ./derby/10.5.3.0/derby-10.5.3.0.jar ./derby/10.5.3.0/derby-10.5.3.0.pom ./derby/maven-metadata-local.xml ./derby-project ./derby-project/10.5.3.0 ./derby-project/10.5.3.0/derby-project-10.5.3.0.pom ./derby-project/maven-metadata-local.xml ./derbyclient ./derbyclient/10.5.3.0 ./derbyclient/10.5.3.0/derbyclient-10.5.3.0.jar ./derbyclient/10.5.3.0/derbyclient-10.5.3.0.pom ./derbyclient/maven-metadata-local.xml ./derbyLocale_cs ./derbyLocale_cs/10.5.3.0 ./derbyLocale_cs/10.5.3.0/derbyLocale_cs-10.5.3.0.jar ./derbyLocale_cs/10.5.3.0/derbyLocale_cs-10.5.3.0.pom ./derbyLocale_cs/maven-metadata-local.xml ./derbyLocale_de_DE ./derbyLocale_de_DE/10.5.3.0 ./derbyLocale_de_DE/10.5.3.0/derbyLocale_de_DE-10.5.3.0.jar ./derbyLocale_de_DE/10.5.3.0/derbyLocale_de_DE-10.5.3.0.pom ./derbyLocale_de_DE/maven-metadata-local.xml ./derbyLocale_es ./derbyLocale_es/10.5.3.0 ./derbyLocale_es/10.5.3.0/derbyLocale_es-10.5.3.0.jar ./derbyLocale_es/10.5.3.0/derbyLocale_es-10.5.3.0.pom ./derbyLocale_es/maven-metadata-local.xml ./derbyLocale_fr ./derbyLocale_fr/10.5.3.0 ./derbyLocale_fr/10.5.3.0/derbyLocale_fr-10.5.3.0.jar ./derbyLocale_fr/10.5.3.0/derbyLocale_fr-10.5.3.0.pom ./derbyLocale_fr/maven-metadata-local.xml ./derbyLocale_hu ./derbyLocale_hu/10.5.3.0 ./derbyLocale_hu/10.5.3.0/derbyLocale_hu-10.5.3.0.jar ./derbyLocale_hu/10.5.3.0/derbyLocale_hu-10.5.3.0.pom ./derbyLocale_hu/maven-metadata-local.xml ./derbyLocale_it ./derbyLocale_it/10.5.3.0 ./derbyLocale_it/10.5.3.0/derbyLocale_it-10.5.3.0.jar ./derbyLocale_it/10.5.3.0/derbyLocale_it-10.5.3.0.pom ./derbyLocale_it/maven-metadata-local.xml ./derbyLocale_ja_JP ./derbyLocale_ja_JP/10.5.3.0 ./derbyLocale_ja_JP/10.5.3.0/derbyLocale_ja_JP-10.5.3.0.jar ./derbyLocale_ja_JP/10.5.3.0/derbyLocale_ja_JP-10.5.3.0.pom ./derbyLocale_ja_JP/maven-metadata-local.xml ./derbyLocale_ko_KR ./derbyLocale_ko_KR/10.5.3.0 ./derbyLocale_ko_KR/10.5.3.0/derbyLocale_ko_KR-10.5.3.0.jar ./derbyLocale_ko_KR/10.5.3.0/derbyLocale_ko_KR-10.5.3.0.pom ./derbyLocale_ko_KR/maven-metadata-local.xml ./derbyLocale_pl ./derbyLocale_pl/10.5.3.0 ./derbyLocale_pl/10.5.3.0/derbyLocale_pl-10.5.3.0.jar ./derbyLocale_pl/10.5.3.0/derbyLocale_pl-10.5.3.0.pom ./derbyLocale_pl/maven-metadata-local.xml ./derbyLocale_pt_BR ./derbyLocale_pt_BR/10.5.3.0 ./derbyLocale_pt_BR/10.5.3.0/derbyLocale_pt_BR-10.5.3.0.jar ./derbyLocale_pt_BR/10.5.3.0/derbyLocale_pt_BR-10.5.3.0.pom ./derbyLocale_pt_BR/maven-metadata-local.xml ./derbyLocale_ru ./derbyLocale_ru/10.5.3.0 ./derbyLocale_ru/10.5.3.0/derbyLocale_ru-10.5.3.0.jar ./derbyLocale_ru/10.5.3.0/derbyLocale_ru-10.5.3.0.pom ./derbyLocale_ru/maven-metadata-local.xml ./derbyLocale_zh_CN ./derbyLocale_zh_CN/10.5.3.0 ./derbyLocale_zh_CN/10.5.3.0/derbyLocale_zh_CN-10.5.3.0.jar ./derbyLocale_zh_CN/10.5.3.0/derbyLocale_zh_CN-10.5.3.0.pom ./derbyLocale_zh_CN/maven-metadata-local.xml ./derbyLocale_zh_TW ./derbyLocale_zh_TW/10.5.3.0 ./derbyLocale_zh_TW/10.5.3.0/derbyLocale_zh_TW-10.5.3.0.jar ./derbyLocale_zh_TW/10.5.3.0/derbyLocale_zh_TW-10.5.3.0.pom ./derbyLocale_zh_TW/maven-metadata-local.xml ./derbynet ./derbynet/10.5.3.0 ./derbynet/10.5.3.0/derbynet-10.5.3.0.jar ./derbynet/10.5.3.0/derbynet-10.5.3.0.pom ./derbynet/maven-metadata-local.xml ./derbytools ./derbytools/10.5.3.0 ./derbytools/10.5.3.0/derbytools-10.5.3.0.jar ./derbytools/10.5.3.0/derbytools-10.5.3.0.pom ./derbytools/maven-metadata-local.xml ./derbywar ./derbywar/10.5.3.0 ./derbywar/10.5.3.0/derbywar-10.5.3.0.pom ./derbywar/10.5.3.0/derbywar-10.5.3.0.war ./derbywar/maven-metadata-local.xml > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747623#action_12747623 ] Rick Hillegas commented on DERBY-4267: -- Thanks Kristian and Julien. I have applied Kristian's 2a patch and added the UTF-8 property to pom.xml as Julien recommended. The following 2 commands produced no errors and reported that they ran successfully: mvn package mvn install This produced a tree of objects under ~/.m2/repository/org/apache/derby. Those artifacts are jars, poms, and maven-metadata-local.xml files. The jars appear to be the correct size. The poms and metadata files appear to be non-vacuous. So far so good I think. Comparing this to the old maven1 process, I now expect that I am supposed to do the following: 1) sign or generate checksums for these artifacts 2) upload the artifacts, signatures, and checksums somewhere Is there a script or set of instructions for doing (1) and (2)? Thanks, -Rick > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[
https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747407#action_12747407
]
Julien HENRY commented on DERBY-4267:
-
To suppress
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
you simply have to define the encoding of your files and set the following
property in the POM.
{code}
UTF-8
{code}
this is a standardized Maven properties that all plugins will use except
compiler plugin that is not yet released.
> Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
> --
>
> Key: DERBY-4267
> URL: https://issues.apache.org/jira/browse/DERBY-4267
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Affects Versions: 10.5.1.1, 10.6.0.0
>Reporter: H.-Dirk Schmitt
> Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat,
> derby-4267-2a-using_ant_task.diff, derby-4267-2a-using_ant_task.stat,
> maven2.zip
>
>
> Only 10.4.2.0 and older are available in the maven 2 repositories.
> May you please also provide the new version.
> Please see also https://issues.apache.org/jira/browse/DERBY-4220
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[
https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737916#action_12737916
]
Kristian Waagan commented on DERBY-4267:
Dag,
Thanks for looking at the patch. Regarding your questions:
a) mvn install: Yes, this must be run from withing the maven2 directory.
b) Correct, the version is inherited and set in the parent pom
("derby-project").
c) filtering: You are correct it should be turned off, if we continue to use
this plugin.
Regarding the warning messages you see, I think they are coming from jar:jar
(jar-default), as I have set the encoding for the resources plugin.
However, I have obviously failed to instruct maven to add the Derby jar files.
We're not following Maven conventions, because we're not using it to build the
artifacts. All that is needed is to tell Maven to use the pre-built jar as the
artifact.
The only way I have managed to do this so far, is to use the antrun plugin with
the ant copy task. It is more of a hack though, since I'm overwriting the
artifact built by Maven itself (which is the almost empty jar you're
mentioning, containing some metadata).
Unless anybody gives me a hint, or provides a better solution, I'm going to add
the other dependencies and switch to using the antrun task.
Also, is there a way to make Maven2 not execute or not try to package anything
for the jar:jar goal?
Help from an experienced Maven2 user would be nice at this point! Help from
not-so-experienced users is also welcome ;)
> Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
> --
>
> Key: DERBY-4267
> URL: https://issues.apache.org/jira/browse/DERBY-4267
> Project: Derby
> Issue Type: Task
> Components: Build tools
>Affects Versions: 10.5.1.1, 10.6.0.0
>Reporter: H.-Dirk Schmitt
> Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat,
> maven2.zip
>
>
> Only 10.4.2.0 and older are available in the maven 2 repositories.
> May you please also provide the new version.
> Please see also https://issues.apache.org/jira/browse/DERBY-4220
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737628#action_12737628 ] Dag H. Wanvik commented on DERBY-4267: -- Hmm, I see several of these warnings when running "mvn install", e.g.: [WARNING] Using platform encoding (ISO8859-1 actually) to copy filtered resources, i.e. build is platform dependent! [WARNING] JAR will be empty - no content was marked for inclusion! something seems wrong. The installed jars seem mostly empty, too. I must be doing something wrong.. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737606#action_12737606 ] Dag H. Wanvik commented on DERBY-4267: -- Thanks for doing this, Kristian! I am new to maven, but I read this helpful intro: http://www.javaworld.com/javaworld/jw-05-2006/jw-0529-maven.html and tried to understand our *.pom's, I also downloaded Maven and tried an "mvn install" (NOTE: this had to be done from inside the maven2 directory, I found), and then it seemed to work: I found the Derby artifacts in my ~/.m2 directory structure. Inspecting the poms, I only found one item which seemed to contradict the intro: The module poms lack , which the intro claim is mandatory, but I did not see any error message, so I suppose it is inherited from the top pom, then? Another question: We specifiy to true; is that needed for Derby? It seems potentially dangerous in that strings inside jars could be replaced? It seems to me the dependencies from locale jars to derby.jar should be included. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: derby-4267-1a-maven2.diff, derby-4267-1a-maven2.stat, > maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736860#action_12736860 ] Kathey Marsden commented on DERBY-4267: --- Hi Kristian, I would like to try to get maven2 updated for the 10.5.2 release. I would like to do whatever I can to help get the procedure finalized, but don't feel at all qualified to answer your questions or review the patch. I will download it and give it a try. Meanwhile here is my feeble input on some of your questions: b) Do we want to keep the M1 stuff around? If we can avoid it I think that would be good. I would say lets just publish maven2 for 10.5.2 and see if anyone complains. c) Where do we put the new files? Does /trunk/maven2 seem like a good place? d) I have defined a dependency between derbynet and derby. Are there more dependencies we should add? I am not sure what the dependency relationship means but there is definitely a relationship between the locale jars and derby.jar and derbyrun.jar and the other jars. e) Do we want to publish derbyTesting? I think it would be useful but don't know if it causes problems for those that download all the jars. Would there be a problem with footprint? I don't think we published it with maven1. f) When publishing a new release, should we update the SubVersion repos URL to be the branch instead of trunk? I think that makes sense. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > Attachments: maven2.zip > > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725225#action_12725225 ] Kathey Marsden commented on DERBY-4267: --- I don't think the 10.5.1.1 release has shown up yet. Probably more useful than getting the release posted for us, would be getting instructions on how to do it ourselves. Kristian, since you started the conversation with the maven folks, could you follow up? I am willing to do the mechanics if we get instructions. It will be good practice for 10.5.2. > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4267) Investigate why Derby 10.5.1.1 is not available in the maven2 repositories
[ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718747#action_12718747 ] Kristian Waagan commented on DERBY-4267: The existing background material for this issue can be found in a d...@maven thread and a derby-...@db thread: http://www.nabble.com/Apache-Derby-artifacts-for-Maven-2-td23958179.html http://www.nabble.com/Maven-artifacts---time-to-move-to-Maven2--td23965723.html To sum up; - automatic conversion of Maven1 artifacts to Maven2 has been stopped - it seems the Maven community will convert the 10.5.1.1 Maven1 artifacts to Maven2 for us (we need to monitor / follow up on this, see [1]) - the Derby community should start producing Maven2 artifacts [1] I think the M2 artifacts should appear here: http://repo1.maven.org/maven2/org/apache/derby/ > Investigate why Derby 10.5.1.1 is not available in the maven2 repositories > -- > > Key: DERBY-4267 > URL: https://issues.apache.org/jira/browse/DERBY-4267 > Project: Derby > Issue Type: Task > Components: Build tools >Affects Versions: 10.5.1.1, 10.6.0.0 >Reporter: H.-Dirk Schmitt > > Only 10.4.2.0 and older are available in the maven 2 repositories. > May you please also provide the new version. > Please see also https://issues.apache.org/jira/browse/DERBY-4220 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
