Hello Daniel,
>> that won't really make too much of a difference. I've set up a POM which
>> takes into account the current project structure.
>
> I know it doesn't help with your short-term goal, but when we build LT with
> mvn, I think we should use the standard directory layout.
That's a good idea. However, the standard layout only includes src/main/java
and src/main/test. I think dev should best go to it's own module. Maybe you are
already planning that. Risking that I repeat other things you already though
about, I'll just mention what else I noticed when I build the POM:
- the i18n properties files are in the regular source folder. In the standard
Maven layout, they should to go to src/main/resources.
- I think that rules and resource would best be kept somewhere under a
org/langaugetool "package" to avoid any potential conflict with other artifacts.
>> Maybe you want to start by having a look at the pom I crafted.
>
> Could you send the URL again? I think the one in your artifact repo looked
> almost empty, i.e. there were no dependencies... maybe I just looked at the
> wrong place.
I am not sure where you were looking. I attached a POM for 1.8 to this issue
https://sourceforge.net/tracker/index.php?func=detail&aid=3564184&group_id=110216&atid=655717
I'll also add one for trunk now to the same issue.
Probably I'll go on with trying to get cjftransform and ictclas4j to Maven
Central next.
Cheers,
-- Richard
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Languagetool-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/languagetool-devel
