Title: Message Title
Lennart Jörelid commented on an issue
Title: Message Title
Lennart Jörelid closed an issue as Fixed
Title: Message Title
Lennart Jörelid commented on an issue
Hi all,
I'd like to release version 1.7 of the AspectJ Maven Plugin, which contains
updates
to the internal AspectJ toolset and several bug fixes.
The AspectJ-Maven-Plugin weaves AspectJ aspects into your classes
using the AspectJ compiler ("ajc").
We solved 6 issues:
http://jira.codehaus.org/se
+1
2014-09-09 18:23 GMT+02:00 Lennart Jörelid :
> Hi all,
>
> I'd like to release version 1.7 of the AspectJ Maven Plugin, which
> contains updates
> to the internal AspectJ toolset and several bug fixes.
>
> The AspectJ-Maven-Plugin weaves AspectJ aspects into your classes
> using the AspectJ co
Folks - I would be really grateful if someone running a Windows box could
perform a build of the A-M-P.
I believe that we have fixed all OS-dependent issues regarding path
definitions in the ITs, but it would be nice to verify this...
:)
And I give a +1, btw.
2014-09-09 18:37 GMT+02:00 David
Hi,
first can you give the correct location to the staging repository cause
i simply can't find it...
I've checked.
https://nexus.codehaus.org/content/repositories/releases/...
https://nexus.codehaus.org/content/groups/staging/org/codehaus/mojo/aspectj-maven-plugin/
Only 1.6 available but N
Let's see here:
a) The privileges in JIRA must have been altered since the last release -
because I can't find the "Release" button in there. Anyone else who can't
access the release button in JIRA?
b) I'll spin a staging repo shortly; when I take a look I can't find it
either. Weird. I'll re-spin
Hi Lennart,
> Let's see here:
a) The privileges in JIRA must have been altered since the last release
- because I can't find the "Release" button in there. Anyone else who
can't access the release button in JIRA?
You need to see if you have Link "Administration" on the upper left
corner righ
Title: Message Title
Brandon Heck created an issue
Current trunk runs fine on my system:
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:28+0100)
Maven home: D:\apache-maven-3.0.5\bin\..
Java version: 1.7.0_55, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_55\jre
Default locale: nl_NL, plat
I see no sign of maven-release-plugin ran. Am I the only one?
latest pom.xml still show 1.7-SNAPSHOT (
https://svn.codehaus.org/mojo/trunk/mojo/aspectj-maven-plugin/pom.xml)
-Dan
On Tue, Sep 9, 2014 at 11:38 AM, Robert Scholte
wrote:
> Current trunk runs fine on my system:
> Apache Maven 3.0.5
Just quoting the ajdoc-ref[1]
"ajdoc currently requires the tools.jar from J2SE 1.3 to be on the
classpath. Normally the scripts set this up, assuming that your JAVA_HOME
variable points to an appropriate installation of Java. You may need to
provide this jar when using a different version
Thanks; found it.
Fixing the release as well. Posting a new release vote when done.
2014-09-09 20:00 GMT+02:00 Karl Heinz Marbaise :
> Hi Lennart,
>
> > Let's see here:
>
>>
>> a) The privileges in JIRA must have been altered since the last release
>> - because I can't find the "Release" button
Title: Message Title
Alejandro E commented on an issue
Nice.
Thanks, Robert.
2014-09-09 20:38 GMT+02:00 Robert Scholte :
> Current trunk runs fine on my system:
> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
> 14:51:28+0100)
> Maven home: D:\apache-maven-3.0.5\bin\..
> Java version: 1.7.0_55, vendor: Oracle Corporation
>
Title: Message Title
Alejandro E edited a comment on an issue
I believe that the error comes from the fact that there is nothing in the
repo (pom/sha-1 or otherwise) for the maven GAV
com.sun:tools:jar:1.7.0_65
It's weird since the dependency states a systemPath.
I would expect maven to simply ignore the GAV resolution and use the file
found at the systemPa
I have tried to perform the release for some time now, and it fails with
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: Commit failed (details follow):
[ERROR] svn: access to
'/mojo/!svn/act/4ff53956-aa6f-40d2-addd-7d1463164bbf' forbidden
Despite my
Somehow I feel that we've got the wrong end of the stick here. I don't think
invoking ajdoc in-process is the right thing to do, and it also defeats maven
toolchains mechanism. I reckon the plugin should instead encapsulate some logic
to build the classpath and detect where the tools.jar (or eq
I guess we could change the way we invoke the ajdoc if we feel there is a
better way to do it.
However, for creating a classpath containing the tools.jar there is a
simple mechanism for this in maven - by using the systemPath property on a
dependency.
2014-09-10 0:23 GMT+02:00 Sergei Ivanov :
>
Title: Message Title
Sergei Ivanov created an issue
Title: Message Title
Lennart Jörelid assigned an issue to Lennart Jörelid
What I mean is: let us get rid of system-scoped dependency completely, because
it is unreliable and potentially disruptive. Let us introduce some logic in the
code of the plugin itself to try an locate the tools.jar (or equivalent) using
the configured java environment and then fork a new java
Title: Message Title
Stefan Bohn commented on an issue
Title: Message Title
Stefan Bohn commented on an issue
Title: Message Title
Lennart Jörelid closed an issue as Fixed
I've traditionally done it when asked, but I'm not really tracking the project
any more. It'd be good if someone could take over the responsibility.
- Brett
On 5 Sep 2014, at 8:21 pm, Arnaud Héritier wrote:
> Ben told me that officially it is Brett who is responsible to create Mojo
> projects
28 matches
Mail list logo
