The source code is available in the sandbox, in head/trunk. You are
looking at a tag which pre-dates the initial check-in of the plugin.
Try .../mojo/trunk/.

If you put macker-rules.xml in src/main/resources, it is automatically
copied to /target/classes during Maven's execution. This is why I
chose this location. If you are running into a problem, please send me
the stack trace and a sample project, and I'll be happy to take a look
at it.

Wayne

On 9/3/07, copernic Jeremy <[EMAIL PROTECTED]> wrote:
> Hi Wayne,
> First of all, thanks for your macker plugin, I just tried it and I have a
> first feedback to share with you.
> But first, I would like to ask you where I could find the source code?
> In fact the source code does not seem available on the svn mojo sandbox
> http://svn.codehaus.org/mojo/tags/mojo-sandbox-4/macker-maven-plugin/
> Then I tried it through a test project and it seems to require that the
> macker-rules.xml file is placed under my /target/classes/ directory instead
> of src/main/resources like stated in the "A Simple
> Example<http://mojo.codehaus.org/macker-maven-plugin/examples/simple.html>"
> section of the web site. Is it possible to change that to the
> src/main/resources directory?
> cheers,
> Jeremy
>
>
>
> On 8/28/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
> >
> > I just now deployed the 1.0.0-SNAPSHOT to Codehaus Snapshot repo. So
> > you could use that instead of downloading and "mvn install" it
> > locally.
> >
> > Wayne
> >
> > On 8/28/07, copernic Jeremy <[EMAIL PROTECTED]> wrote:
> > > Hi Wayne,
> > > First of all, thanks for  your updates!
> > > I was a little bit busy these last days with personal stuff  so I wasn't
> > > able to try it at all.
> > > But now that I am back, I'll try it right away.
> > > Thanks again and be sure that I'll keep you informed of it.
> > >
> > > Jeremy
> > >
> > >
> > > On 8/27/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
> > > > Just FYI... The code is available in the Mojo sandbox SVN and the site
> > > > was just deployed:
> > > > http://mojo.codehaus.org/macker-maven-plugin/
> > > >
> > > > Wayne
> > > >
> > > > On 8/20/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
> > > > > Jeremy et al,
> > > > >
> > > > > I just checked in the first rough draft of macker-maven-plugin
> > > > > v1.0.0-SNAPSHOT into Mojo sandbox.
> > > > >
> > > > > Please grab the source, mvn -U install site, take a look at the site
> > > > > docs to figure out how to use/configure it, and give it a try. You
> > can
> > > > > use mvn macker:macker package to test it on your own project once
> > > > > you're included the plugin in <build><plugins> and installed the
> > > > > plugin into your local repo.
> > > > >
> > > > > As I said before, I appreciate your feedback.
> > > > >
> > > > > Wayne
> > > > >
> > > > > On 8/20/07, copernic Jeremy <[EMAIL PROTECTED]> wrote:
> > > > > > Hi Wayne,
> > > > > > That's a great news for the community!
> > > > > > Please let us informed ASAP when your M2 Macker plugin is
> > available on
> > > the
> > > > > > Mojo sandbox, and I'll try to give you some feedback of it.
> > > > > > regards,
> > > > > >
> > > > > > Jeremy
> > > > > >
> > > > > >
> > > > > > On 8/17/07, Wayne Fay < [EMAIL PROTECTED]> wrote:
> > > > > > >
> > > > > > > I've seen enough people asking for a M2 Macker plugin in the
> > last
> > > few
> > > > > > > months/year that I finally decided to go ahead and write one
> > myself.
> > > > > > > In my limited testing, it works great, but I am not really a
> > Macker
> > > > > > > user so I'll need some feedback from people to improve it.
> > > > > > >
> > > > > > > I will be submitting it to the Mojo sandbox shortly. I will post
> > > > > > > another message when it is available -- you will need to
> > download
> > > the
> > > > > > > code and "mvn install" it on your own machine before using it,
> > just
> > > > > > > like all plugins in the sandbox.
> > > > > > >
> > > > > > > Just wanted to let you know. For now, the rules need to be
> > stored in
> > > > > > > an external macker-rules.xml file but I will see about allowing
> > the
> > > > > > > configuration directly in the pom.xml file as well.
> > > > > > >
> > > > > > > Wayne
> > > > > > >
> > > > > > > On 8/13/07, copernic Jeremy <[EMAIL PROTECTED]> wrote:
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > just to let you know some updates on my maven-macker-plugin
> > issue:
> > > > > > > > I was not able to use the maven-macker-plugin available on
> > repo1
> > > > > > > >
> > > http://repo1.maven.org/maven2/maven-plugins/maven-macker-plugin/
> > > > > > > > In fact I found a link explaining how to use Macker with Maven
> > 2
> > > through
> > > > > > > the
> > > > > > > > maven-antrun-plugin.
> > > > > > > >
> > > http://docs.codehaus.org/display/MAVENUSER/Running+Macker+with+Maven+2
> > > > > > > > It works fine for now but I must admit that I would prefer
> > using a
> > > full
> > > > > > > > maven-macker-plugin without any ant tasks and build.xml files.
> > > > > > > > I think it could be great if we could define all the
> > macker.xml's
> > > rules
> > > > > > > > directly into the pom.xml of the maven project, or simply
> > specify
> > > the
> > > > > > > > location of the macker.xml file like the JettyConfig file
> > style.
> > > > > > > Something
> > > > > > > > like that:
> > > > > > > >
> > > > > > > >   <plugin>
> > > > > > > >
> > > <groupId>maven-plugins</groupId>
> > > > > > > >
> > > <artifactId>maven-macker-plugin</artifactId>
> > > > > > > >                          <version>0.4.2</version>
> > > > > > > >                          <configuration>
> > > > > > > >
> > > > > > > >
> > > <mackerConfig>${basedir}src/test/macker.xml</mackerConfig>
> > > > > > > >                         </configuration>
> > > > > > > >
> > > > > > > >
> > > > > > > >  </plugin>
> > > > > > > >
> > > > > > > > or
> > > > > > > >
> > > > > > > >
> > > > > > > >   <plugin>
> > > > > > > >
> > > <groupId>maven-plugins</groupId>
> > > > > > > >
> > > <artifactId>maven-macker-plugin</artifactId>
> > > > > > > >                          <version>0.4.2</version>
> > > > > > > >                          <configuration>
> > > > > > > >                            <macker>
> > > > > > > >                              <rulesets>
> > > > > > > >                                    <ruleSet>
> > > > > > > >
> > > <accessRule>
> > > > > > > >
> > > <from>myClass</from>
> > > > > > > >
> > > <to>someJavaClass</to>
> > > > > > > >
> > > </accessRule>
> > > > > > > >                                    </ruleSet>
> > > > > > > >                                </ruleSets>
> > > > > > > >
> > > > > > > >                                  .....
> > > > > > > >                              </macker>
> > > > > > > >                         </configuration>
> > > > > > > >
> > > > > > > >
> > > > > > > >  </plugin>
> > > > > > > >
> > > > > > > > Maybe someday, someone who knows well Macker and the
> > development
> > > of
> > > > > > > maven
> > > > > > > > plugins could try release one like that?!
> > > > > > > > Yet, the main Macker developper is aware of these issue and
> > > suggestions
> > > > > > > and
> > > > > > > > he told me that he would suggest them for a futur release so
> > lets
> > > hope!
> > > > > > > >
> > > > > > > > regards,
> > > > > > > >
> > > > > > > > Jeremy
> > > > > > > >
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > 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]

Reply via email to