Yes, the second part of my mail :)
See the section "Temporary workaround during the next week".
Op 15-02-11 09:02, Jervis Liu schreef:
Hi Geoffrey, I got following errors when I build guvnor, did I miss
anything?
[WARNING] Could not transfer metadata
org.eclipse.wst.sse:core/maven-metadata.xm
l from
maven-repository.dev.java.net
(
http://download.java.net/maven/1): No conn
ector available to access repository
maven-repository.dev.java.net
(
http://downl
oad.java.net/maven/1) of type legacy using the available factories
WagonReposito
ryConnectorFactory
[ERROR] The build could not read 4 projects -> [Help 1]
[ERROR]
[ERROR] The project
org.drools:guvnor-repository-connector-jackrabbit:5.2.0-SN
APSHOT
(D:\svn\drools\guvnor\guvnor-repository-connector\guvnor-repository-conne
ctor-jackrabbit\pom.xml) has 1 error
[ERROR] 'dependencies.dependency.version' for
org.drools:guvnor-repository-c
onnector-jcr:jar is missing. @ line 19, column 17
[ERROR]
[ERROR] The project
org.drools:guvnor-repository-connector-modeshape:5.2.0-SNA
PSHOT
(D:\svn\drools\guvnor\guvnor-repository-connector\guvnor-repository-connec
tor-modeshape\pom.xml) has 1 error
[ERROR] 'dependencies.dependency.version' for
org.drools:guvnor-repository-c
onnector-jcr:jar is missing. @ line 19, column 17
[ERROR]
[ERROR] The project org.drools:guvnor-repository:5.2.0-SNAPSHOT
(D:\svn\drools
\guvnor\guvnor-repository\pom.xml) has 2 errors
[ERROR] 'dependencies.dependency.version' for
org.drools:guvnor-repository-c
onnector-jcr:jar is missing. @ line 51, column 17
[ERROR] 'dependencies.dependency.version' for
org.drools:guvnor-repository-c
onnector-jackrabbit:jar is missing. @ line 99, column 21
[ERROR]
[ERROR] The project org.drools:guvnor-webapp:5.2.0-SNAPSHOT
(D:\svn\drools\guv
nor\guvnor-webapp\pom.xml) has 2 errors
[ERROR] 'dependencies.dependency.version' for
org.drools:guvnor-repository:j
ar is missing. @ line 148, column 17
[ERROR] 'dependencies.dependency.version' for
org.drools:droolsjbpm-ide-comm
on:jar is missing. @ line 172, column 17
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please rea
d the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildin
gException
On 2011/2/14 21:25, Geoffrey De Smet wrote:
> The split-off of guvnor is done, the repository is ready to be used.
> See below how to get started.
>
> But before you get started, please *check these settings*:
>
> * *Do not include @author tags in new files*
> o For motivation see:
>
https://issues.jboss.org/browse/JBRULES-2869
> o All author tags have been stripped (done during split-up)
> * *Line endings are unix (\n)*
> o All files now have unix line endings (done during split-up)
> * *Do not use tab characters (\t)*
> o All flies now use spaces instead of tabs (done during
> split-up)
> * Encoding for all files (except property files) is UTF-8
> o Not changes during split-up
>
> For detailed instructions on how to configure this fast correctly,
> see the README.txt file, currently still at:
>
https://github.com/droolsjbpm/droolsjbpm/blob/master/README.txt#L118
>
>
> How to get started
> ============
>
> // Close eclipse/intellij
> cd ~/projects
> // Move the old repostory out of the way
> mv droolsjbpm monolitic-droolsjbpm
> // Make a directory to hold all the new repositories
> mkdir droolsjbpm
> cd droolsjbpm
> git clone git@github.com:droolsjbpm/guvnor.git guvnor
> git clone git@github.com:droolsjbpm/droolsjbpm-tools.git droolsjbpm-tools
> // As the split-up continues, you'll be able to add more repo's
> // Make a new workspace in Eclipse/IntelliJ
> // Add each of the new repo's as maven projects to that new workspace
>
>
> Temporary workaround during the next week
> ============================
>
> Because the split-up is still ongoing (not everything split up yet +
> the hudson jobs don't deploy snapshot yet),
> you 'll need to do this to get it to work, because the repo's still
> depend on the old parent pom for now:
>
> cd ~/projects
> // go the old repo and get it up to date
> cd monolitic-droolsjbpm
> git pull --rebase
> // Just build and install the parent pom
> mvn clean install -N
> cd ..
> cd droolsjbpm
> cd guvnor
> mvn clean install -DskipTests
> cd ..
> cd droolsjbpm-tools
> mvn clean install -DskipTests
>
>
> Status of split-up
> ===========
>
> Guvnor and droolsjbpm-tools are unfrozen and mostly ready.
> Integration is starting now, might take till tomorrow.
> Drools will be started Wednesday.
> droolsjbpm-knowledge and droolsjbpm-parent will be started later this
> week
> drools-planner has to be redone.
> droolsjbpm-dist will be started after those.
> General cleanup and improvements can run into next week.
> --
> With kind regards,
> Geoffrey De Smet
>
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev