"subArray is not a member of scala.runtime.BoxedArray"
Hi all, I get this error when I try to use subArray in the latest Maven builds of 2.8.0 (updated an hour ago), > val arr = Array(2, 3, 4) > arr.subArray(0, 3) exception when typing line1$object.$iw.$iw.arr().subArray value subArray is not a member of scala.runtime.BoxedArray in file scala.tools.nsc.symtab.Types$TypeError: value subArray is not a member of scala.runtime.BoxedArray at scala.tools.nsc.typechecker.Contexts$Context.error(Contexts.scala:314) at scala.tools.nsc.typechecker.Infer$Inferencer.error(Infer.scala:270) Thanks so much, Nicholas https://ntung.com
bootstrapping (cyclic dependencies with different versions)
Hi all, Maven seems to be complaining about having cycles in the graph, even if I specify different versions for resources. This is rather unfortunate; bootstrapping is a good technique (and not cyclic if one uses previous versions), and should not be restricted arbitrarily. If anyone knows a workaround, I'd appreciate it. Google search shows scm:bootstrap, but this looks unrelated. Thanks in advance, Nicholas https://ntung.com smime.p7s Description: S/MIME Cryptographic Signature
Re: quick question: remove .timestamp on "mvn clean"
On Thu, Jul 23, 2009 at 2:43 AM, Martin Höller wrote: > On Thursday 23 July 2009 Nicholas Tung wrote: > > Hi all, > > > >Does anyone know how to remove the .timestamp on "mvn > > clean"? If I don't, it doesn't rebuild Scala files. > > Configure the maven-clean-plugin to delete this additional file: > > http://maven.apache.org/plugins/maven-clean-plugin/examples/delete_additional_files.html > > hth, > - martin > Thanks! Nicholas https://ntung.com
Re: maven scala plugin troubles -- scalac compiler plugin
On Wed, Jul 22, 2009 at 7:00 PM, Josh Suereth wrote:
> Hey, I just go this email. I'll make the patch and commit shortly. Thanks
> for the submission!
>
> There's still some mismatch since we re-built the scala-tools.org server,
> so the maven-scala-plugin nightlies are not getting published. I'm going to
> try to resolve that shortly.
>
> - Josh
Thanks very much! Please adjust the code style as you see fit. I'm not sure
whether it's worth reusing the addToClasspath() call, if it's just creating
a Set and adding a single element to it.
regards,
Nicholas
>
>
> On Wed, Jul 22, 2009 at 4:14 PM, Nicholas Tung wrote:
>
>> The problem is that my scala plugin project has additional dependencies.
>> These are added to pluginClassPath, but then you only add the first element
>> from pluginClassPath (why the first? this seems a bit arbitrary).
>>
>> If you wouldn't mind fixing this (in github master), I'd appreciate it
>> very much. I don't think users would ever want to add deps of the project as
>> plugins, so perhaps the changes below would work.
>>
>> Also, is the latest version on a public site?
>>
>> regards,
>> Nicholas
>> https://ntung.com
>>
>> +protected void addToClasspath(BasicArtifact artifact_info,
>> +Set classpath, boolean add_deps) throws Exception
>> +{
>> +addToClasspath(factory.createArtifact(artifact_info.groupId,
>> +artifact_info.artifactId, artifact_info.version,
>> +Artifact.SCOPE_RUNTIME, "jar"), classpath, add_deps);
>> +}
>>
>> +protected void addToClasspath(Artifact artifact, Set
>> classpath,
>> +boolean add_deps) throws Exception
>> +{
>> resolver.resolve(artifact, remoteRepos, localRepo);
>> classpath.add(artifact.getFile().getCanonicalPath());
>> -for(Artifact dep: resolveArtifactDependencies(artifact)) {
>> -classpath.add(dep.getFile().getCanonicalPath());
>> +if (add_deps) {
>> +for (Artifact dep : resolveArtifactDependencies(artifact)) {
>> +classpath.add(dep.getFile().getCanonicalPath());
>> +}
>> }
>> }
>>
>> +/**
>> + * Retrieves a list of paths to scala compiler plugins.
>> + * @return The list of plugins
>> + * @throws Exception
>> + */
>> +private Set getCompilerPlugins() throws Exception {
>> +Set plugins = new HashSet();
>> +if (compilerPlugins != null) {
>> +Set ignoreClasspath = new HashSet();
>> +addToClasspath(SCALA_GROUPID, "scala-compiler", scalaVersion,
>> +ignoreClasspath);
>> +addToClasspath(SCALA_GROUPID, SCALA_LIBRARY_ARTIFACTID,
>> +scalaVersion, ignoreClasspath);
>> +for (BasicArtifact artifact : compilerPlugins) {
>> +System.out.println("compiler plugin: " +
>> artifact.toString());
>> + // TODO - Ensure proper scala version for plugins
>> +Set pluginClassPath = new HashSet();
>> +addToClasspath(artifact, pluginClassPath, false);
>> +pluginClassPath.removeAll(ignoreClasspath);
>> +plugins.addAll(pluginClassPath);
>> +}
>> +}
>> +return plugins;
>> +}
>>
>>
>> On Wed, Jul 22, 2009 at 12:43 PM, Nicholas Tung
>> wrote:
>>
>>> It looks like you're setting this stuff with javadoc... imho, an
>>> attribute is a bit more robust. Also, you have
>>>
>>>
>>> instead of , but changing it doesn't
>>> seem to help (it then compiles without any plugin).
>>>
>>> If you could point me to other relevant code (I'm looking at
>>> ScalaMojoSupport.java), that would be much appreciated.
>>>
>>> Thanks in advance,
>>> Nicholas
>>> https://ntung.com
>>>
>>> On Wed, Jul 22, 2009 at 12:12 PM, Nicholas Tung
>>> wrote:
>>>
>>>> Hi Josh,
>>>>
>>>> Thanks; the repo is at [1], and I've attached the plugin (though I
>>>> suspect it has more to do with command line compilation rather than the
>>>> plugin itself).
>>>>
>>>> I might end up overriding the main compiler class (i.e. not
>>>> scala.tools.nsc.Main), so I could probably hack something from there.
>>&
quick question: set version for deploy
Hi all, Is there a way to set the version for the "mvn deploy" command? I tried -Dversion=, and -Dproject.version=, and that didn't do anything. Alternately (maybe even better), is there a command line to bump [set] the version number in a project and all modules? I see there is the versions plugin to update dependencies, but that's not quite what I want. Also, there appear to be bugs when using variables inside the parent pom.xml for the tag. Thanks in advance, Nicholas https://ntung.com
quick question: remove .timestamp on "mvn clean"
Hi all, Does anyone know how to remove the .timestamp on "mvn clean"? If I don't, it doesn't rebuild Scala files. thanks, Nicholas https://ntung.com
Re: maven scala plugin troubles -- scalac compiler plugin
The problem is that my scala plugin project has additional dependencies.
These are added to pluginClassPath, but then you only add the first element
from pluginClassPath (why the first? this seems a bit arbitrary).
If you wouldn't mind fixing this (in github master), I'd appreciate it very
much. I don't think users would ever want to add deps of the project as
plugins, so perhaps the changes below would work.
Also, is the latest version on a public site?
regards,
Nicholas
https://ntung.com
+protected void addToClasspath(BasicArtifact artifact_info,
+Set classpath, boolean add_deps) throws Exception
+{
+addToClasspath(factory.createArtifact(artifact_info.groupId,
+artifact_info.artifactId, artifact_info.version,
+Artifact.SCOPE_RUNTIME, "jar"), classpath, add_deps);
+}
+protected void addToClasspath(Artifact artifact, Set classpath,
+boolean add_deps) throws Exception
+{
resolver.resolve(artifact, remoteRepos, localRepo);
classpath.add(artifact.getFile().getCanonicalPath());
-for(Artifact dep: resolveArtifactDependencies(artifact)) {
-classpath.add(dep.getFile().getCanonicalPath());
+if (add_deps) {
+for (Artifact dep : resolveArtifactDependencies(artifact)) {
+classpath.add(dep.getFile().getCanonicalPath());
+}
}
}
+/**
+ * Retrieves a list of paths to scala compiler plugins.
+ * @return The list of plugins
+ * @throws Exception
+ */
+private Set getCompilerPlugins() throws Exception {
+Set plugins = new HashSet();
+if (compilerPlugins != null) {
+Set ignoreClasspath = new HashSet();
+addToClasspath(SCALA_GROUPID, "scala-compiler", scalaVersion,
+ignoreClasspath);
+addToClasspath(SCALA_GROUPID, SCALA_LIBRARY_ARTIFACTID,
+scalaVersion, ignoreClasspath);
+for (BasicArtifact artifact : compilerPlugins) {
+System.out.println("compiler plugin: " +
artifact.toString());
+// TODO - Ensure proper scala version for plugins
+Set pluginClassPath = new HashSet();
+addToClasspath(artifact, pluginClassPath, false);
+pluginClassPath.removeAll(ignoreClasspath);
+plugins.addAll(pluginClassPath);
+}
+}
+return plugins;
+}
On Wed, Jul 22, 2009 at 12:43 PM, Nicholas Tung wrote:
> It looks like you're setting this stuff with javadoc... imho, an attribute
> is a bit more robust. Also, you have
>
>
> instead of , but changing it doesn't seem
> to help (it then compiles without any plugin).
>
> If you could point me to other relevant code (I'm looking at
> ScalaMojoSupport.java), that would be much appreciated.
>
> Thanks in advance,
> Nicholas
> https://ntung.com
>
> On Wed, Jul 22, 2009 at 12:12 PM, Nicholas Tung wrote:
>
>> Hi Josh,
>>
>> Thanks; the repo is at [1], and I've attached the plugin (though I
>> suspect it has more to do with command line compilation rather than the
>> plugin itself).
>>
>> I might end up overriding the main compiler class (i.e. not
>> scala.tools.nsc.Main), so I could probably hack something from there.
>>
>> I got github master to build... if you could tell me where things are,
>> I'd appreciate it.
>>
>> regards,
>> Nicholas
>> https://ntung.com
>>
>> [1] http://github.com/gatoatigrado/skalch/tree/master
>>
>>
>> On Wed, Jul 22, 2009 at 8:34 AM, Josh Suereth
>> wrote:
>>
>>> Does your scalac plugin depend on any other plugins? If you can point me
>>> towards a repository holding your scalac plugin, I can create an integration
>>> test for this use case. I'm adding it to the list of known issues.
>>>
>>> - Josh
>>>
>>>
>>> On Wed, Jul 22, 2009 at 2:43 AM, Nicholas Tung
>>> wrote:
>>>
>>>> Hi David and Josh,
>>>>
>>>>I'm having some trouble with the maven scala plugin; it doesn't seem
>>>> to be setting the -Xplugin line correctly when I try to build a project
>>>> [1].
>>>> The configuration passed to the maven-scala-plugin is [2]. I'm running
>>>> $(mvn
>>>> install -Dmaven.scala.displayCmd=true).
>>>>
>>>> Feel free to look at the pom.xml files if you want [3], but don't
>>>> feel obliged... I haven't done proper Scala / Java separation yet (among
>>>> other things to clean it up).
>>>>
>>>>
Re: help with maven-dependency-plugin
2009/7/21 Thomas Scheffler
> Hi,
>
> I am using the maven-dependency-plugin to build a big jar file out of
> direct
> dependencies (code below). If that big jar file is a dependency of another
> project all direct dependencies are also copied over. I just want to copy
> the
> transitive dependencies of the big jar file.
>
> I tried to mark the dependencies of the big jar file with scope "provided"
> but
> then also the transitive dependency got marked as "provided".
>
> I am at wits' end now. Can the big jar file mark direct dependencies as
> "provided" but copy the dependencies of it as its own dependencies somehow?
>
> regards
>
> Thomas
>
>
> maven-dependency-plugin
>
>
> unpack-dependencies
> process-resources
>
>unpack-dependencies
>
>
>
> ${project.build.directory}/classes
>true
>
> LICENSE*, NOTICE*, META-INF/LICENSE*, META-INF/NOTICE*,
> license, license/**/*, test, test/**/*,
> WEB-INF/web.xml,
> WEB-INF/log4j.*,
> WEB-INF/lib, WEB-INF/lib/**/*,
> WEB-INF/classes, WEB-INF/classes/**/*
>
>
>
>
>
>
>
So you have, e.g.,
M --> (A, B)
A --> { D }
B --> { E }
and you want
jar(A, B) --> { D, E }
How do jar files express dependencies? Are you trying to create a project
which then doesn't need to download any more subprojects?
You could also use the assembly plugin to generate the jar file; you can
then specify which modules to include. Maybe you could also manually copy
dependencies from A and B to M?
regards,
Nicholas
https://ntung.com
maven scala plugin troubles -- scalac compiler plugin
Hi David and Josh, I'm having some trouble with the maven scala plugin; it doesn't seem to be setting the -Xplugin line correctly when I try to build a project [1]. The configuration passed to the maven-scala-plugin is [2]. I'm running $(mvn install -Dmaven.scala.displayCmd=true). Feel free to look at the pom.xml files if you want [3], but don't feel obliged... I haven't done proper Scala / Java separation yet (among other things to clean it up). Thanks so much! Nicholas https://ntung.com [1] version 2.10 gives -Xplugin:/home/gatoatigrado/.m2/repository/org/scala-tools/maven-scala-plugin/2.10/maven-scala-plugin-2.10.jar version 2.11 gives -Xplugin:/home/gatoatigrado/.m2/repository/xom/xom/1.1/xom-1.1.jar the correct version should be -Xplugin:/home/gatoatigrado/.m2/repository/edu/berkeley/cs/sketch/skalch-plugin/git-master/skalch-plugin-git-master.jar [2] edu.berkeley.cs.sketch skalch-plugin git-master [3] http://github.com/gatoatigrado/skalch/tree/master
Re: help with multi-module build
On Tue, Jul 21, 2009 at 10:47 PM, Nicholas Tung wrote: > On Tue, Jul 21, 2009 at 10:21 PM, David C. Hicks wrote: > >> One of the tenets of Maven is to create one artifact for each module. >> Combining your source in the same directory tree violates that tenet. >> I'm sure you can probably force Maven to do it, but it won't like it. >> When you specify the you are essentially telling Maven to look >> for pom.xml files in those sub-directories. > > > Right... I moved the plugin code to its own subdirectory [1], but no > difference (I agree it's cleaner though). > > It's possible that using "mvn compile" could be part of your problem. >> When you only run the "compile" goal, you don't get to the "package" >> goal, which is when the jar file would be created. > > > I tried "package", and only "install" seems to have the correct effect of > building the jar file. I suppose it's probably not going to hurt to install > versus package... it just seems weird. > > After I do that, I get some "NoSuchElementException" from scala, but I'm > guessing that's the scala maven plugin's fault. The jar appears to be > correct. > yeah, I'm pretty sure it's maven-scala's fault [1]. unfortunately I can't build 2.12 from github due to some dependency problems. The original problem of "execute `mvn package` for one module to compile another" would be interesting to solve, but I think the above is a more critical issue... Thanks for your help, Nicholas [1] version 2.10 gives -Xplugin:/home/gatoatigrado/.m2/repository/org/scala-tools/maven-scala-plugin/2.10/maven-scala-plugin-2.10.jar version 2.11 gives -Xplugin:/home/gatoatigrado/.m2/repository/xom/xom/1.1/xom-1.1.jar the correct version should be -Xplugin:/home/gatoatigrado/.m2/repository/edu/berkeley/cs/sketch/skalch-plugin/git-master/skalch-plugin-git-master.jar
Re: help with multi-module build
On Tue, Jul 21, 2009 at 10:21 PM, David C. Hicks wrote: > One of the tenets of Maven is to create one artifact for each module. > Combining your source in the same directory tree violates that tenet. > I'm sure you can probably force Maven to do it, but it won't like it. > When you specify the you are essentially telling Maven to look > for pom.xml files in those sub-directories. Right... I moved the plugin code to its own subdirectory [1], but no difference (I agree it's cleaner though). It's possible that using "mvn compile" could be part of your problem. > When you only run the "compile" goal, you don't get to the "package" > goal, which is when the jar file would be created. I tried "package", and only "install" seems to have the correct effect of building the jar file. I suppose it's probably not going to hurt to install versus package... it just seems weird. After I do that, I get some "NoSuchElementException" from scala, but I'm guessing that's the scala maven plugin's fault. The jar appears to be correct. regards, Nicholas [1] http://github.com/gatoatigrado/skalch/commit/5163b21d82736045806adab40d2b607d59e9bfc5 > > > > Nicholas Tung wrote: > > On Tue, Jul 21, 2009 at 9:47 PM, David C. Hicks > wrote: > > > > > >> It's hard to say from your description, but it sounds like you need to > >> do some serious restructuring of your project. Here's what I think you > >> need to have: > >> > >> base-of-project/ > >>pom.xml > >> > >>myproj-plugin/ > >>pom.xml > >>src/main/scala code goes here > >> > >>myproj-base/ > >>pom.xml > >>src/main/other code goes here > >> > > > > > > This unnecessarily separates java code in myproj-base from myproj-plugin, > > but sure. > > > > > > > >> The pom.xml in the base directory would have your section and > >> look like this: > >> > >> > >>myproj-plugin > >>myproj-base > >> > >> > > > > > > I'm using this exactly [1] > > > > > > > >> This is where the pom.xml files in each sub-directory come into play. > >> The pom.xml in myproj-base would list "myproj-plugin" as a dependency. > >> You assign the groupId, artifactId, and version to myproj-plugin in the > >> top of its pom.xml. Then you can reference that artifact just like you > >> would any other artifact. The difference is that Maven knows to find it > >> inside the reactor during the build. > >> > > > > > > I'm already doing this as well [2]; thanks anyway though. > > > > It is far better to bend your expectations to the way that Maven wants > > > >> to work than to try to force it into submitting to the way YOU want to > >> do things. Just learn new habits and you will be far happier letting > >> Maven do all the neat things it does for you for free. > >> > > > > > > I'm very willing to restructure the project (i.e. move actual locations > of > > source files around). However, I don't see any advantage if Maven won't > do > > things differently. Will it actually build the jar for one project when I > > type mvn compile? I am specifying one project as the dependency of > another > > using the standard group-artifact-version tags [3]. > > > > Maven is already correctly building (mvn compile) myproj-plugin before > > myproj-base. However, it isn't packaging it as a jar for the Maven Scala > > plugin. > > > > Thanks so much, > > Nicholas > > > > [1] > > > http://github.com/gatoatigrado/skalch/blob/9e1d2d0fd05c3fd9c7fbbfadfbe44b1bfa31b388/pom.xml#L43 > > [2] > > > http://github.com/gatoatigrado/skalch/blob/9e1d2d0fd05c3fd9c7fbbfadfbe44b1bfa31b388/skalch-base/pom.xml#L52 > > [3] > > > http://github.com/gatoatigrado/skalch/blob/9e1d2d0fd05c3fd9c7fbbfadfbe44b1bfa31b388/skalch-base/pom.xml#L34 > > > > >
Re: help with multi-module build
On Tue, Jul 21, 2009 at 9:47 PM, David C. Hicks wrote: > It's hard to say from your description, but it sounds like you need to > do some serious restructuring of your project. Here's what I think you > need to have: > > base-of-project/ >pom.xml > >myproj-plugin/ >pom.xml >src/main/scala code goes here > >myproj-base/ >pom.xml >src/main/other code goes here This unnecessarily separates java code in myproj-base from myproj-plugin, but sure. > The pom.xml in the base directory would have your section and > look like this: > > >myproj-plugin >myproj-base > I'm using this exactly [1] > This is where the pom.xml files in each sub-directory come into play. > The pom.xml in myproj-base would list "myproj-plugin" as a dependency. > You assign the groupId, artifactId, and version to myproj-plugin in the > top of its pom.xml. Then you can reference that artifact just like you > would any other artifact. The difference is that Maven knows to find it > inside the reactor during the build. I'm already doing this as well [2]; thanks anyway though. It is far better to bend your expectations to the way that Maven wants > to work than to try to force it into submitting to the way YOU want to > do things. Just learn new habits and you will be far happier letting > Maven do all the neat things it does for you for free. I'm very willing to restructure the project (i.e. move actual locations of source files around). However, I don't see any advantage if Maven won't do things differently. Will it actually build the jar for one project when I type mvn compile? I am specifying one project as the dependency of another using the standard group-artifact-version tags [3]. Maven is already correctly building (mvn compile) myproj-plugin before myproj-base. However, it isn't packaging it as a jar for the Maven Scala plugin. Thanks so much, Nicholas [1] http://github.com/gatoatigrado/skalch/blob/9e1d2d0fd05c3fd9c7fbbfadfbe44b1bfa31b388/pom.xml#L43 [2] http://github.com/gatoatigrado/skalch/blob/9e1d2d0fd05c3fd9c7fbbfadfbe44b1bfa31b388/skalch-base/pom.xml#L52 [3] http://github.com/gatoatigrado/skalch/blob/9e1d2d0fd05c3fd9c7fbbfadfbe44b1bfa31b388/skalch-base/pom.xml#L34
help with multi-module build
Hi all, I'm having trouble getting a multi-module project to build. What I want to do is simple: build a Scala compiler plugin (jar), and then compile the rest of the project using that. Right now, I have two proxy modules (building things in ../src), "myproj-plugin" and "myproj-base". The first builds only the plugin, using an assembly to build the jar file -- the output looks fine (though the name is a bit long, and I'm not sure how to properly address it). However, when "myproj-base" builds, I get "unable to find resource " [1], and it tries downloading "myproj-plugin" from the Scala and Maven repositories (ick). I tried specifying the jar name path with "systemPath", but no luck. If possible, I'd like it to be able to - rebuild all Scala files in "myproj-base" when the plugin changes (to make sure the plugin doesn't break anything). - build the entire project by typing "mvn compile" in the base directory (from scratch). The full project source is at [2]. Thanks in advance, Nicholas Sorry if this is a duplicate; I have gmail configured to send as nt...@ntungbut was subscribed as gatoatigr...@gmail [1] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] wrap: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: [2] http://github.com/gatoatigrado/skalch/commit/cb258d39c0dc796de8f6c1076e05505bb21f854a
help with multi-module build
Hi all, I'm having trouble getting a multi-module project to build. What I want to do is simple: build a Scala compiler plugin (jar), and then compile the rest of the project using that. Right now, I have two proxy modules (building things in ../src), "myproj-plugin" and "myproj-base". The first builds only the plugin, using an assembly to build the jar file -- the output looks fine (though the name is a bit long, and I'm not sure how to properly address it). However, when "myproj-base" builds, I get "unable to find resource " [1], and it tries downloading "myproj-plugin" from the Scala and Maven repositories (ick). I tried specifying the jar name path with "systemPath", but no luck. If possible, I'd like it to be able to - rebuild all Scala files in "myproj-base" when the plugin changes (to make sure the plugin doesn't break anything). - build the entire project by typing "mvn compile" in the base directory (from scratch). The full project source is at [2]. Thanks in advance, Nicholas btw. spam filter is giving me bouncebacks even though I am registered on the list. [1] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] wrap: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: [2] http://github.com/gatoatigrado/skalch/commit/cb258d39c0dc796de8f6c1076e05505bb21f854a
Re: scalac compiler plugin help
On Tue, Jun 2, 2009 at 17:31, Wayne Fay wrote: > > Thanks, I tried that, and 2.9, 2.10, etc. It seems to give the same > error. > > Your pom is missing groupId, artifactId, and version, so add those > too. That will most likely fix it. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > Thanks so much, that definitely fixes the first error. Sorry to be such a newbie. The error messages should be better than NullPointerException though. I kind-of fixed the some others; updates at http://www.gatoatigrado.com/tmp-code-snippets . However, I still get, [WARNING] you don't define org.scala-lang:scala-library as a dependency of the project which seems odd, as I have scala-library designated as a dependency of the project. I would like to run a build of Scala git head (Scala 2.8) if possible... this is probably on the documentation somewhere... On Tue, Jun 2, 2009 at 17:37, Martin Gainty wrote: > > David- > inside the main pom.xml located at > /tmp/gatoatigrado/maven/maven-scala-plugin/src/it/docTest/pom.xml Sorry, gatoatigrado [me, Nicholas] is the user, David is the developer of the Maven Scala plugin. Thanks though, it helps (see updates on page linked above). kind regards, Nicholas
Re: scalac compiler plugin help
On Tue, Jun 2, 2009 at 17:06, Wayne Fay wrote: > >I'm trying to use the Maven to build a scala project, but I get a > > NullPointerException at > > > "org.apache.maven.artifact.versioning.DefaultArtifactVersion.parseVersion". > > My setup is at http://www.gatoatigrado.com/tmp-code-snippets. > > If you go to the repo and click thru to the versions directory for the > plugin [1], you'll see various versions of this plugin available, with > the latest being 2.10.1. I'd add that to the > node and try again. Also, it is a good practice to always > declare versions for plugins as well as dependencies. > > It seems like the documentation should probably be updated as well, > but you'll have to take that up with the author of the plugin. > > [1] > http://scala-tools.org/repo-releases/org/scala-tools/maven-scala-plugin/ > Thanks, I tried that, and 2.9, 2.10, etc. It seems to give the same error. I cc'd David Bernard (he's the developer listed on github). Thanks in advance, Nicholas
scalac compiler plugin help
Hi all, I'm trying to use the Maven to build a scala project, but I get a NullPointerException at "org.apache.maven.artifact.versioning.DefaultArtifactVersion.parseVersion". My setup is at http://www.gatoatigrado.com/tmp-code-snippets. Other attempts: I also had some problems building the plugin from git ( http://github.com/davidB/maven-scala-plugin/tree/master), though it doesn't seem like compiling the plugin it is necessary. Using the configuration at http://scala-tools.org/mvnsites/maven-scala-plugin/usage_scalac_plugins.html, and adding the tag as per http://scala-tools.org/mvnsites/maven-scala-plugin/usage.html didn't work either. Please update the plugin page with a working example. Thanks in advance, Nicholas
Re: [minor] tar archives extraction warning
opensuse x64 64b, originally 11.1 but I'm tracking trunk, so probably closer to 11.2 now. oliver:~> tar --version tar (GNU tar) 1.21 regards, Nicholas On Tue, Jun 2, 2009 at 13:43, Olivier Lamy wrote: > Hi, > What is your os ? > > -- > Olivier > > 2009/6/2 Nicholas Tung : > > I get "tar: A lone zero block at 6491" when extracting either the .tar.gz > or > > .tar.bz2 files. The md5sum matches. It doesn't seem to be a problem. > > > > Nicholas > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
[minor] tar archives extraction warning
I get "tar: A lone zero block at 6491" when extracting either the .tar.gz or .tar.bz2 files. The md5sum matches. It doesn't seem to be a problem. Nicholas
