[
https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4267:
-----------------------------------
Attachment: derby-4267-1a-maven2.stat
derby-4267-1a-maven2.diff
Thanks for the comments, Kathey.
I'm definitely not a Maven expert either, so join the club :)
I have attached patch 1a, which contains the following improvements;
- builds artifacts for the localizations and the derby.war servlet
- added a settings.xml (for deployment)
Some more comments;
> 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.
We're currently not shipping derbyrun.jar, and I intend to skip that for the
first iteration of the move from M1 to M2.
I think defined dependencies are mandatory, so they would have to be from the
various locale jars to derby.jar? It guess it would be safe to skip this step
for the time being as well.
> 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.
It is correct that we haven't published it with M1. Since nobody has requested
it, maybe we can skip / postpone this too.
FYI, here are some very brief instructions:
- apply patch
- modify relevant properties and metadata
(for a release, I guess this is derby.version and specifying the correct
path for the source code in svn, i.e replacing trunk with branches/10.5)
- build: mvn install
(this installs the artifacts in your local cache/repos)
- deploy to Apache repository:
- first edit settings.xml
- mvn deploy
- sign files etc as specified in the release process document
I think as soon as the files are up on the server, they can't (or aren't
allowed to) be deleted.
A first step of the testing is to ensure the jar files are included and that
the content of the poms look good, which can be done in the local cache and/or
the source files.
Note that the file permissions has been set to 644, which was stated in a
readme I found on the Apache server. The reasoning behind this is perhaps that
a different person than the one who deployed the artifacts shouldn't be allowed
to change them.
For directories, the permissions should be 775.
> 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.
