You're welcome to file a bug where ever you deem it to be appropriate.
I am simply a pragmatist -- filing a bug against the plugin will
actually result in a fix for your issue much more quickly. This is
clearly a defect in the plugin, and so the change can be incorporated
rather quickly.
Filing a bug of this nature against the Maven project itself may (or
may not) result in a change in the 2.1.x series which is currently in
the planning stages. The reason you're seeing this problem is related
to the "system scope" which you're generally advised to avoid and
which many people believe should be deprecated.
[Another quick fix would be to simply create a link (ln -s) from
classes.jar to tools.jar in the location the plugin expects it to
exist.]
Wayne
On 5/17/07, David Leangen <[EMAIL PROTECTED]> wrote:
Thank you for this.
You're right. The appropriate thing to do would be to remove the system
dependency. There should be a generalized maven project that acts as an
abstraction to the system's tools.jar. This project could then be
included as a dependency by any project that needs to use classes from
tools.jar.
Given that Maven is supposed to be a generalized build tool, I don't
think it's reasonable (unless there's really some reason to do so) to
have to create build profiles just because the OS changes.
In this respect, the bug should be filed against maven itself, and not
against the plugin. wdyt?
Cheers,
Dave
On Wed, 2007-05-16 at 22:50 -0500, Wayne Fay wrote:
> This issue has come up previously regarding JAX-WS. The fix at that
> time was to actually remove the system-scoped tools.jar dependency
> from the plugin pom (IIRC -- check the Archives for more details).
>
> So you will probably need to file a bug against the native2ascii
> plugin requesting a similar modification. Or if you're the only Mac
> user, just adjust the plugin pom.xml file in your local cache to
> remove the tools.jar dependency (this is a hack).
>
> Wayne
>
> On 5/16/07, David Leangen <[EMAIL PROTECTED]> wrote:
> >
> > Hello!
> >
> > I am having some issues with mojo plugin for native2ascii in a
> > multi-platform setting.
> >
> > The problem is with the dependency on tools.jar, as per the text below.
> >
> > On the Mac, there is no tools.jar, and all the classes are already
> > included in the classpath by default. Therefore, native2ascii fails on
> > Mac with a message asking to install "com.sun:tools:jar:dummy".
> >
> >
> > Any ideas how I can get this to work on ALL my machines?
> >
> > Thank you!
> >
> >
> > <dependencies>
> > <dependency>
> > <groupId>com.sun</groupId>
> > <artifactId>tools</artifactId>
> > <version>1.4.2</version>
> > <scope>system</scope>
> > <systemPath>${java.home}/../lib/tools.jar</systemPath>
> > </dependency>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
