What will happen to cross references if we move ? (Relations to other
issues in differnt projects, relations to plexus issues)
Kristian
2015-01-07 8:20 GMT+01:00 Hervé BOUTEMY :
> ok
> who can prepare a little VM with Jira 6.3.4? Can infra?
>
> and how to get Codehaus content? Any maven dev with
+1
the little issue with Maven 2.2.1 found by Karl Heinz doesn't deserve stopping
the process: order isn't critical, and it is not failing with Maven 3
I take this issue like a good example of why we should finish our latest
releases for Maven 2.2.1 then switch to Maven 3 (and JDK 6 while at it
ok
who can prepare a little VM with Jira 6.3.4? Can infra?
and how to get Codehaus content? Any maven dev with knowledge and karma?
I'm interested to try the process on MPLUGIN [1]
then be ready for later any Mave developer to do the same for each and every
Jira project
notices:
1. account ded
Am 2015-01-06 um 21:04 schrieb Karl Heinz Marbaise:
Hi,
i have checked SHA1 Ok.
Checked with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.1, 3.2.5
but unfortunately found the following with Maven 2.2.1:
20:03:35 [INFO] [checkstyle:check {execution: checkstyle-check}]
20:03:36 [INFO]
20:03:36 [INFO] There a
Hi,
i have checked SHA1 Ok.
Checked with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.1, 3.2.5
but unfortunately found the following with Maven 2.2.1:
20:03:35 [INFO] [checkstyle:check {execution: checkstyle-check}]
20:03:36 [INFO]
20:03:36 [INFO] There are 9 checkstyle errors.
20:03:36 [INFO] [jarsigner:ve
Conclusion: We're off to 1.6-land !
- Update to jdk 6.0 "at will", but please be sure that we're not
leaving the last 1.5 version in a regressed state.
- Minor version bump for jdk 1.6 upgrade, remember to tag jira version
as "First 1.6 version" (in manage versions)
- To achieve this it is probabl
