Ondra,
as
https://github.com/windup/windup/wiki/Rules-Create-a-Basic-Java-based-Rul...
shows a template for new add-on, forge-addon should be in provided scope.
I think we probably need to review the whole project if that is correct
everywhere.
I don't see a reason why it could require it in compile scope.
On 16.4.2016 01:02, Ondrej Zizka wrote:
Hi,
I've noticed that in the pom.xml of $subj, there is:
<dependency>
<groupId>org.jboss.windup.ast</groupId>
<artifactId>windup-java-ast</artifactId>
<classifier>forge-addon</classifier>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.jboss.windup.rules.apps</groupId>
<artifactId>windup-rules-base</artifactId>
<classifier>forge-addon</classifier>
<scope>compile</scope>
</dependency>
Shouldn't that be of scope provided, and listed in ../addon/pom.xml ?
Ondra
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
--
Marek Novotny
--
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno